Added Facility Image Form (API URL needed)

[anuran-roy]

This PR addresses Issues #2131 and #2171.

Except the Backend API, other frontend components are ready to be used.

Screenshots:

[rithviknishad]

@anuran-roy deploy preview is failing. merge the latest develop branch.

[rithviknishad]

@anuran-roy I've cleared cache and triggered deploy. but still it's failing :/
I can also see that you do have the latest develop here...

[nihal467]

@anuran-roy @rithviknishad @gigincg the deploy is still failed

[netlify]

❌ Deploy Preview Failed. CC: @rithviknishad

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

[rithviknishad]

@anuran-roy @nihal467 deploy fails even after clear cache and deploy.

[vercel]

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

Name	Status	Preview	Updated
care-fe	✅ Ready (Inspect)	Visit Preview	Jun 11, 2022 at 2:34PM (UTC)

[anuran-roy]

@nihal467 actually this PR is awaiting the backend changes to be merged by Marmik. It requires an endpoint, which is yet to be added to care backend.

[rithviknishad]

@gigincg @anuran-roy Vercel preview deploy works without clearing cache out of the box for this PR.
However netlify preview build failed 3 times even after clearing cache.

Build logs says:

8:03:16 PM: Different build command detected, going to use the one specified in the Netlify
configuration file: 'CI='' yarn run build' versus 'CI="" yarn run prebuild && CI="" yarn run
build || { cat /tmp/* ; sleep 30 ; false; }' in the Netlify UI

[nihal467]

@anuran-roy is it good for testing

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

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information