add: disable none volunteers assigning

[kunatastic]

closes #2695 and #2771

Updation

[vercel]

@kunatastic is attempting to deploy a commit to the Coronasafe Team on Vercel.

A member of the Team first needs to authorize it.

[netlify]

❌ Deploy Preview Failed. CC: @rithviknishad

Name	Link
🔨 Latest commit	5f22fe3
🔍 Latest deploy log	https://app.netlify.com/sites/care-net/deploys/62a6c8fbd998c80008d36564

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
care-fe	❌ Failed (Inspect)		Jun 19, 2022 at 5:25PM (UTC)

[patelaryan7751]

LGTM

[arpancodes]

We may not want to show the ✔️ beside the last selected volunteer after we clear? even after changing the volunteer...

we may use something else like a background colour to show it was last selected... the ✔️ gives an impression that it is already selected but the form won't submit.

[kunatastic]

Also #2771 has been resolved in same PR

[nihal467]

@kunatastic test failed,

if i assign a volunteer to a patient once, and it unable to unassign the patient from volunteer by clicking clear and submit button is not possible.

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret 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.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	Secret	Commit	Filename
757392	Google API Key	2cec8ae	src/Common/env.tsx	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 secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
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.

---

<sup>🦉 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.

Our GitHub checks need improvements? Share your feedbacks!</sup>

[nihal467]

@kunatastic what is the PR status

[mathew-alex]

👋 Hi, @kunatastic,
Conflicts have been detected against the base branch. Please rebase your branch against the base branch.

---

This message is automatically generated by prince-chrismc/label-merge-conflicts-action so don't hesitate to report issues/improvements there.

[stale]

Hi, @${author}, This pr/issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs for 7 more days. Thank you for your contributions.

[stale]

Hi, @gigincg, @nihal467, @khavinshankar, @mathew-alex This pr/issue has been automatically closed because it has not had any recent activity. Thank you for your contributions. Feel free to repopen the pr/issue.