docs: synchronizing README from snyk/user-docs

[team-cli-bot]

Automatic PR controlled by GitHub Action

[CatalinSnyk]

This one looks odd.

[CatalinSnyk]

Hey @aluca3, could you take a look at the comment I left? This update seems to introduce some new templating in the markdown file that does not play out really well in our repo.

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[snyk-pr-review-bot]

PR Reviewer Guide 🔍

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Formatting Regression 🟡 [minor] The PR replaces a standard Markdown **Note:** prefix with GitBook-specific tags {% hint style="info" %} and {% endhint %}. These tags are not part of GitHub Flavored Markdown (GFM) and will render as literal text when viewed on GitHub, which degrades the readability of the primary documentation for the repository. While these tags work in the GitBook-based user-docs source, the root README.md on GitHub should ideally maintain compatibility with standard Markdown. {% hint style="info" %} Before you can use the CLI for Open Source scanning, you must install your package manager. The needed third-party tools, such as Gradle or Maven, must be in the `PATH`. {% endhint %}

📚 Repository Context Analyzed This review considered 6 relevant code sections from 5 files (average relevance: 0.82) README.md (2 segments, lines 1-100) help/cli-commands/README.md (lines 1-82) help/cli-commands/container.md (lines 1-16) help/cli-commands/code.md (lines 1-14) help/cli-commands/iac.md (lines 1-21)