Add support for shallow cloning azcore.Client instances (#21065)

[jhendrixMSFT]

This allows for multiple clients to share the same underlying pipeline while having the correct client name string in traces.

This is a cherry-pick of 1d8ba7b with a slightly modified CHANGELOG to reflect the current sequence of releases. The feature's implementation has also been slightly changed as the current incarnation in main was built on features added in the v1.7.0-beta series.

[jhendrixMSFT]

We have a bit of a problem here. The latest preview of armmonitor is using [email protected] for fakes and tracing. Removing that content breaks the dependency check. While we can override it here, I don't believe we can in the release pipeline.

I see a few options.

• Fix dependency checking. This is ideal but seems difficult with release week coming up.
• Add a flag to CI to allow skipping of dependency checking.
• Release azcore as v1.6.2 instead of v1.7.0.

Frankly, releasing as v1.6.2 simplifies the upcoming releases but that violates semver rules. So I think the only option at present is bullet 2 unless folks thing that fixing dependency checking to account for this scenario can happen in the next few days. Thoughts?

[jhendrixMSFT]

Opened #21116 to track the CI issue.

[jhendrixMSFT]

@benbp what's the correct way for me to rerun this with the flag Skip.DependencyCheck set to true?

[benbp]

@jhendrixMSFT you can't manually set variables in our public pipeline project for security reasons. However, you can run the internal version of this pipeline and then override approvals from the public failure. Go to the pipeline, click Run pipeline, set the branch to be refs/pull/21098/merge, then click Variables and add your variable value.

NOTE: as it's manually run, the internal pipeline will try to create a release stage, but you can just deny that, or also set a Skip.Release variable to true

[jhendrixMSFT]

/check-enforcer override