chore: canary fixture updates

[adityathebe]

resolves: #289

[netlify]

✅ Deploy Preview for flanksource-docs ready!

Name	Link
🔨 Latest commit	0885fea
🔍 Latest deploy log	https://app.netlify.com/sites/flanksource-docs/deploys/670660112a79080008692a1a
😎 Deploy Preview	https://deploy-preview-292--flanksource-docs.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 configuration.

[netlify]

✅ Deploy Preview for canarychecker canceled.

Name	Link
🔨 Latest commit	0885fea
🔍 Latest deploy log	https://app.netlify.com/sites/canarychecker/deploys/67066011a362ff0008503dec

[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	GitGuardian status	Secret	Commit	Filename
13982848	Triggered	Basic Auth String	fb64d8b	canary-checker/docs/reference/1-http.mdx	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.

---

^{🦉 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.}

[moshloop]

@adityathebe - I think the canary-cgecker module might need updating - also check the lint errors

[adityathebe]

@adityathebe - I think the canary-cgecker module might need updating - also check the lint errors

@moshloop it was due to the fixture imports on secret-management doc.

That same file is on two different depths inside mission-control doc and the import path fails on one but is valid on another.

Left that file unchanged for now.