Moved YAUS/ C4GT 22' repo to current monorepo

[homosapien14]

Description: PR to add the frontend repo code developed as part of C4GT" 22

Changes updated all the file structure of YAUS/C4GT'22 Backend as well as frontend.

reference : https://github.com/Samagra-Development/yaus/issues/52

[gitguardian[bot]]

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

🔎 Detected hardcoded secrets in your pull request

| GitGuardian id | Secret | Commit | Filename | | | -------------- | ------------------------- | ---------------- | --------------- | -------------------- | | [-](https://dashboard.gitguardian.com/incidents/secrets) | Generic High Entropy Secret | 40a5d197807245656707fcc38bf398a459964f85 | yaus_c4gt_frontend/.env | [View secret](https://github.com/Samagra-Development/yaus/commit/40a5d197807245656707fcc38bf398a459964f85#diff-c83473e7375c6a39697c4787f017b699L2) | | [-](https://dashboard.gitguardian.com/incidents/secrets) | Generic High Entropy Secret | f874aaecec16da0442d2453962205a0138667503 | yaus_c4gt_frontend/.env | [View secret](https://github.com/Samagra-Development/yaus/commit/f874aaecec16da0442d2453962205a0138667503#diff-c83473e7375c6a39697c4787f017b699R2) | | [-](https://dashboard.gitguardian.com/incidents/secrets) | Generic High Entropy Secret | 87b480fead7920f5fdcd075a94992f6f89de6562 | yaus_c4gt_sdk/sdk-generation/.env | [View secret](https://github.com/Samagra-Development/yaus/commit/87b480fead7920f5fdcd075a94992f6f89de6562#diff-d31edf9531b34b6c8ea73dbff2a6f2c2R1) |

🛠 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](https://blog.gitguardian.com/secrets-api-management?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) the best practices. 3. Revoke and [rotate these secrets](https://docs.gitguardian.com/secrets-detection/detectors/generics/generic_high_entropy_secret#revoke-the-secret?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). 4. If possible, [rewrite git history](https://blog.gitguardian.com/rewriting-git-history-cheatsheet?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). 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](https://blog.gitguardian.com/secrets-api-management/?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) for managing and storing secrets including API keys and other credentials - install [secret detection on pre-commit](https://docs.gitguardian.com/ggshield-docs/integrations/git-hooks/pre-commit?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) 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>

[homosapien14]

hi @Shruti3004 , can you please help me to resolve security conflict and review all the changes?

[homosapien14]

I have updated required changes but still getting this conflict.

[Nazi-pikachu]

Hi @homosapien14 I am also working on migrating the frontend code to monorepo. Based on my exprience with the codebase till now i can suggest you that you should first start with refracting the frontend optionally you can fork my fork so that we can collaborate on this ticket. This way it will get closed earlier instead of having multiple PRs doing the same. Regards