Azcore separate tracer

[kjg]

• Fixes [Tracing] Allow Client libraries to configure schema URL #23307

• This PR allows a schemaURL to be passed to the NewTracer function so that consumers can create tracers that use a different schemaURL than azcore.

• It updates azcore to use the otel semconv package that sets a schemaURL and then uses the semconv Constances for the span keys that have defined semconv keys.

This PR also adds a WithCoreTracerName function to the azcore client so the consumers that do want to do custom tracing can make azcore using azcore's module name and version for the HTTP tracing, and their own module name and version for their portion of the tracing. Using WithCoreTracerName only changes the values used for tracing to azcore values, it still leaves the passed in module name and version for use with the HTTP User Agent header.

I chose this approach because it looks like many of the consumers of this client

• The purpose of this PR is explained in this or a referenced issue.
• The PR does not update generated files.
  • These files are managed by the codegen framework at Azure/autorest.go.
• Tests are included and/or updated for code changes.
• Updates to module CHANGELOG.md are included.
• MIT license headers are included in each file.

[github-actions]

Thank you for your contribution @kjg! We will review the pull request and get back to you soon.

[kjg]

I'm not sure how to make the dependency check pass since I can't update tracing/azotel version of azcore and account for the breaking change until the change is merged and a new version released. Any guidance on how to approach that?