Add sample workflow for reauthentication after risk event

[pankajtaneja5]

🛠 What was changed

Added a new sample workflow: ReauthenticationAfterRiskEventWorkflow.
This workflow demonstrates an adaptive authentication pattern where users are required to reauthenticate after suspicious activity — such as login from a new device or after completing account recovery.

The worker listens for a reauth_complete signal, and the workflow can be configured with a timeout to handle cases where reauthentication isn't completed in time.

🔐 Why?

This use case is relevant for security-conscious applications that need to enforce reauthentication following risk events.
The sample highlights how Temporal can model secure, stateful authentication workflows that are durable, auditable, and cleanly separated from business logic.

It aligns with modern security practices around risk-based session validation and account protection.

✅ Checklist

• New sample added to samples-python
• Demonstrates secure workflow pattern using Temporal signals and timeouts
• Includes worker and starter code for demonstration

Notes

There wasn’t a separate issue filed for this PR.
If preferred, I can open one and link it here for tracking purposes.

Let me know if any adjustments are needed!

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

PANKAJ TANEJA seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}