fix: Network Module Changes

[Abdul-Microsoft]

Purpose

• This pull request refactors the networking setup in infra/main.bicep to use a new virtualNetwork module instead of the previous network module. It also introduces a Bastion Host, a Jumpbox VM, and a VM maintenance configuration for improved security and compliance. All references to networking outputs across dependent modules have been updated to use outputs from the new virtualNetwork module. This change improves modularity, clarity, and compliance with Azure best practices.

Networking architecture overhaul:

• Replaced the previous network module with a new virtualNetwork module, updating all dependent resource references to use outputs from virtualNetwork.
• Updated references in modules for private DNS zones, Cosmos DB, PostgreSQL, Key Vault, OpenAI, Computer Vision, Speech Service, Search, Web, Admin Web, Function, Form Recognizer, Content Safety, Storage, and deployment scripts to use outputs from virtualNetwork instead of network [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17].

Security and compliance enhancements:

• Added modules for Azure Bastion Host and a Jumpbox VM to enable secure access to resources in private networks.
• Introduced a VM maintenance configuration module to comply with PSRule.Rules.Azure requirements.

Tagging and metadata:

• Added a SecurityControl: 'Ignore' tag to the resource group tags for improved resource metadata management.

Minor improvements:

• Refactored the backendUrl variable assignment for improved readability.

Does this introduce a breaking change?

• Yes
• No

How to Test

• Get the code

git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install

• Test the code

What to Check

Verify that the following are valid

• ...

Other Information