add non-binary gender type to constants

[Ritesh-Aggarwal]

This PR fixes an uncaught error which was causing isLoading state to never set to false which caused profile page to get stuck on loading screen ( #2723 ).

[vercel]

@Ritesh-Aggarwal is attempting to deploy a commit to the Coronasafe Team on Vercel.

A member of the Team first needs to authorize it.

[nihal467]

@Ritesh-Aggarwal

unable to create a non-binary gender user

[nihal467]

@Ritesh-Aggarwal test failed

the non-binary is missing from user creation form

[Ritesh-Aggarwal]

• https://care.coronasafe.in/user/add
  There was a discrepancy in GENDER_CHOICES in frontend and backend.
  Now the frontend has been updated to same choices as it is saved in backend. That is "Other" has been changed to "Non-Binary".

[nihal467]

test approved

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