Add VM Deployment Template and Debugging Documentation

[sjdevgo]

Description:

This PR introduces a fully functional Azure Bicep deployment template for virtual machine configuration, accompanied by debugging documentation that records the troubleshooting process encountered during local development and Azure CLI integration.

---

Changes Summary:

Files Added:

• main.bicep: Core Bicep template defining VM deployment configurations.
• azuredeploy.parameters.json: Deployment parameters file for customizing deployment values.
• main.json: Compiled ARM template generated from the Bicep file.
• README.md: Comprehensive deployment guide, including setup instructions and debugging logs.
• metadata.json: Metadata file providing descriptive information about the template for indexing.

---

Details:

Deployment Highlights:

• Resource Group Scope: Configures a virtual machine deployment using Azure Bicep.
• Parameterization: Uses best practices for parameter definition and secure value handling.

---

Documentation Highlights:

• Azure CLI Setup: Instructions for installing and configuring Azure CLI and Bicep tools.
• Troubleshooting Records: Step-by-step records of resolving issues like Azure subscription errors, local deployment failures, and permission conflicts.
• Resolution Path: Documented all resolutions, including creating custom roles, validating templates, and adjusting the deployment pipeline.

---

Contribution Guide Compliance:

• File Naming: Follows required file naming conventions (main.bicep, azuredeploy.parameters.json, metadata.json).
• Folder Structure: Template placed in the quickstarts/vm-deployment-with-custom-config folder.
• Metadata Format: Conforms to Azure template standards for metadata and search indexing.
• Documentation Standard: Provided a comprehensive README.md using GitHub-flavored Markdown as recommended.

---

Please review the submission and provide feedback if additional adjustments are required. Thank you!

[Lime-Cocoa]

Hello, we are also working on rt-thread kernel fuzz testing recently. Have you solved this problem? And I want to know whether it is feasible to use syzkaller to test the kernel of rt-thread?