Remove admitted_to filter

[Ashesh3]

Closes #2642
Backend change: coronasafe/care#841

The attribute this filter is referring to is removed from the backend, hence applying this filter fails. This change will remove the filter from the UI and also clean it up from the backend.

[netlify]

❌ Deploy Preview Failed. CC: @rithviknishad

Name	Link
🔨 Latest commit	71d4496
🔍 Latest deploy log	https://app.netlify.com/sites/care-net/deploys/62a0d3ac2a37690009d5bcda

[aeswibon]

@Ashesh3 I think we need to add this filter in the backend because @aparnacoronasafe opened an issue #2752 regarding this filter.

[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]

@Ashesh3 what is the PR status

[Ashesh3]

@Ashesh3 what is the PR status

Backend change was merged, We can proceed to test out this PR.

[netlify]

✅ Deploy Preview for care-egov-staging ready!

Name	Link
🔨 Latest commit	f89065a
🔍 Latest deploy log	https://app.netlify.com/sites/care-egov-staging/deploys/62e613b617db330008d3cba3
😎 Deploy Preview	https://deploy-preview-2659--care-egov-staging.netlify.app/
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
1 Code Smell

No Coverage information
0.7% Duplication

[nihal467]

@Ashesh3 @gigincg is the admit_to filter getting removed or not, i can see @aparnacoronasafe comments been mentioned in it, can i get some clarity on this PR

[Ashesh3]

Dependent PR: coronasafe/care#924

[mathew-alex]

👋 Hi, @Ashesh3,
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.

[khavinshankar]

@Ashesh3 is the issue fixed, why was this pr closed?

[Ashesh3]

@Ashesh3 is the issue fixed, why was this pr closed?

Yep, this was fixed by @sainak on the backend and as for the frontend, @aparnacoronasafe stated removing the admitted to isn't an option so this PR is not applicable.