{ACR} az acr connected-registry: test cases update

[rosanch]

Description
Expanding az acr connected-registry test capabilities.

---

This checklist is used to make sure that common guidelines for a pull request are followed.

• The PR title and description has followed the guideline in Submitting Pull Requests.

• I adhere to the Command Guidelines.

• I adhere to the Error Handling Guidelines.

[rosanch]

@zhoxing-ms could I please get some guidance with the testing? Why is it not passing the test online but it does on my local machine?

[yonzhan]

@zhoxing-ms to help with

[zhoxing-ms]

@rosanch Could you invite me to participate in the development of your forked repo? I will the re-record yaml for you and upload it to this PR

[wangzelin007]

LGTM

[zhoxing-ms]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[rosanch]

@rosanch Could you invite me to participate in the development of your forked repo? I will the re-record yaml for you and upload it to this PR

@zhoxing-ms did you have any access issues?

[zhoxing-ms]

@rosanch There is no permission problem.
I found that this issue is caused by the fact that the VCR did not record the get_token_from_id(cmd, connected_registry.parent.sync_properties.token_id) requests sent by acr connected-registry permissions show command.
This is usually caused by the inconsistency between the recorded yaml and the latest code. I re-recorded the yaml to solve this issue.