AVNM NSG + UDR Management Swagger changes for stable version

[jbgorthy]

ARM (Control Plane) API Specification Update Pull Request

Tip

Overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

PR review workflow diagram

Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

Purpose of this PR

What's the purpose of this PR? Check the specific option that applies. This is mandatory!

• New resource provider.
• New API version for an existing resource provider. (If API spec is not defined in TypeSpec, the PR should have been created in adherence to OpenAPI specs PR creation guidance).
• Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
• Update existing version to fix OpenAPI spec quality issues in S360.
• Convert existing OpenAPI spec to TypeSpec spec (do not combine this with implementing changes for a new API version).
• Other, please clarify:
  • Contributing to a stable API version for microsft.network. These specs have already been approved in the private repo https://github.com/Azure/azure-rest-api-specs-pr/pull/18788 https://github.com/Azure/azure-rest-api-specs-pr/pull/18849

Due diligence checklist

To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

• I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
• I have reviewed following Resource Provider guidelines, including
  ARM resource provider contract and
  REST guidelines (estimated time: 4 hours).
  I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.

Additional information

Viewing API changes

For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures

If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.

Getting help

• First, please carefully read through this PR description, from top to bottom. Please fill out the Purpose of this PR and Due diligence checklist.
• If you don't have permissions to remove or add labels to the PR, request write access per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories
• To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
• For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
  and https://aka.ms/ci-fix.
• For help with ARM review (PR workflow diagram Step 2), see https://aka.ms/azsdk/pr-arm-review.
• If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
  This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
• If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

[openapi-pipeline-app]

Next Steps to Merge

✅ All automated merging requirements have been met! To get your PR merged, see aka.ms/azsdk/specreview/merge.

[openapi-pipeline-app]

Generated ApiView

Language	Package Name	ApiView Link
Go	sdk/resourcemanager/network/armnetwork	https://apiview.dev/Assemblies/Review/1b263a329090477991c0a7b7b0ae21d7?revisionId=64b5ad6953434735a480481cd71ddf54
Java	azure-resourcemanager-network-generated	https://apiview.dev/Assemblies/Review/d496e631581f47bcab5c961219fc2258?revisionId=a93aacd4cc974c78b1a69ced1dba87e4
JavaScript	@azure/arm-network	https://apiview.dev/Assemblies/Review/c13fd66ecbcc4c2a9995c8a1f4187240?revisionId=0984f2bb21d44b43a69f8ae803c98bf7
.Net	Azure.ResourceManager.Network	https://apiview.dev/Assemblies/Review/806ead8231374028b5c49cb90e200641?revisionId=6b5940fcf21743c0966140585bfec946
Swagger	Microsoft.Network	https://apiview.dev/Assemblies/Review/9a91f46aa0a846acaae91aba821517fb?revisionId=38f4a6979fc8429fbef5d38e0cf13599

[jbgorthy]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[jbgorthy]

This pr is a copy/paste of two PRs that have already been approved in the private specs repo:
https://github.com/Azure/azure-rest-api-specs-pr/pull/18849
https://github.com/Azure/azure-rest-api-specs-pr/pull/18788

The first commit is an exact copy/paste of these files and should not require additional review.

The last commit adds suppressions for two errors that were encountered in the public repo, but not the private. Justification for suppressions are:

1. BodyTopLevelProperties - This looks like a false alarm to me, we are returning a list response to the customer with the expected 'value' and 'nextLink' properties as is recommended in https://github.com/cloud-and-ai-microsoft/resource-provider-contract/blob/master/v1.0/get-resource.md
2. SystemDataDefinitionsCommonTypes - All specs in microsoft.network use a systemData type defined in the network.json file. If we use the one defined in common types, then it causes a duplicate model error in dotnet sdk generation. For now we will use the one in network.json until all of these microsoft.network migrate to the common type ref.

[rkmanda]