Disable role assignment check for vnet for Azure Spring Cloud

[gavinfish]

---

Disable role assignment check for vnet for Azure Spring Cloud. As checking role assignments for target VNet needs permissions to call AAD, this may block some customers in extreme circumstance when their az account does not have such permissions.

General Guidelines

• Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
• Have you run python scripts/ci/test_index.py -q locally?

For new extensions:

• My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish

There is a pipeline to automatically build, upload and publish extension wheels.
Once your PR is merged into master branch, a new PR will be created to update src/index.json automatically.
The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify src/index.json.

[azuresdkci]

If this PR is for a new extension or change to an existing extension, use the following to try out the changes in this PR:

docker run -it microsoft/azure-cli:latest
export EXT=<NAME>
pip install --upgrade --target ~/.azure/cliextensions/$EXT "git+https://github.com/VSChina/azure-cli-extensions.git@jieshe/disable-permission-check#subdirectory=src/$EXT&egg=$EXT"

[yungezz]

hi @fengzhou-msft could you pls help to review? thanks.

[yungezz]

hi @gavinfish even removing the check in Azure CLI side, will there be authorization check at service side, such as NRP?

[yungezz]

LGTM

[gavinfish]

hi @gavinfish even removing the check in Azure CLI side, will there be authorization check at service side, such as NRP?

Yes, this will be checked from service side with specific SP.