Integration test for secret ops

[akhilmhdh]

Description 📣

1. This PR adds api integration test for all secret operations from external entities which includes dashboard, service token (cli) and identity token(sdk)
2. Fixed seed file issue faced when running seeding
3. Resolved a small bug in secret deletion
4. Added ci for running integration test

Type ✨

• Bug fix
• New feature
• Breaking change
• Documentation

Tests 🛠️

# Here's some code block to paste some code snippets

---

• I have read the contributing guide, agreed and acknowledged the code of conduct. 📝

[gitguardian]

⚠️ GitGuardian has uncovered 7 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	GitGuardian status	Secret	Commit	Filename
-		Generic High Entropy Secret	678306b	backend/src/db/seed-data.ts	View secret
-		Generic High Entropy Secret	f09c48d	backend/src/db/seed-data.ts	View secret
-		Generic Private Key	ccaa9fd	backend/e2e-test/routes/v3/secrets.spec.ts	View secret
-		Generic Private Key	ccaa9fd	backend/e2e-test/routes/v3/secrets.spec.ts	View secret
-		Generic Private Key	35d589a	backend/e2e-test/routes/v1/identity.spec.ts	View secret
-		Generic Private Key	2996efe	backend/e2e-test/routes/v1/identity.spec.ts	View secret
-		Generic High Entropy Secret	d428fd0	.env.test.example	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 secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
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>

[DanielHougaard]

Great work, I left a few comments for you!

[maidul98]

Just some structuring comments

[maidul98]

lgtm