Notebook optional user input

[MarianoMolina]

Why are these changes needed?

I've noticed a few threads online asking about how to enable the agents to ask for user input, so I created this notebook that uses a similar StateFlow example to other ChatGroup notebooks, but adds a keyphrase to the system prompts and checks for it in the speaker_selection_method() to optionally ask the user for feedback if the agent needs help.

Related issue number

Answers: https://github.com/microsoft/autogen/discussions/1288

Checks

• [x] I've included any doc changes needed for https://microsoft.github.io/autogen/. See https://microsoft.github.io/autogen/docs/Contribute#documentation to build and test documentation locally.
• [x] I've added tests (if relevant) corresponding to the changes introduced in this PR. -> No tests added, let me know if I should
• [x] I've made sure all auto checks have passed.

[gitguardian[bot]]

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard. Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
10404662	Triggered	Generic CLI Secret	eff19acf1365e34fe17d9ac0939666f32b3ceda5	.github/workflows/dotnet-release.yml	View secret
10404662	Triggered	Generic CLI Secret	e973ac38ea4f7b36687ea03aa44f770d7e2ddcac	.github/workflows/dotnet-release.yml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[MarianoMolina]

I think there are some base branch discrepancies, my commit seems to be making changes despite me fetching main and just adding the notebook file. I've tried a few times to ensure the commit is clean, and its still these 2 files for some reason.

[rysweet]

@MarianoMolina we've rebased and updated this branch for you - have a look at the remaining unresolved reviews and green the CI and we can get this reviewed and merged for you.

[rysweet]

@MarianoMolina - second notice - think this is close - please have a look and make some updates and we can move toward merging.