Implement a Service Bus Shared Access Key Credential

[v-hongli1]

Fix issue #16465

1. Add and change class and test case for implement a Service Bus Shared Access Key Credential
2. Add and change files:
   1). sdk/identity/azure-identity/src/main/java/com/azure/identity/ServiceBusSharedKeyCredential.java
   2). sdk/identity/azure-identity/src/main/java/com/azure/identity/ServiceBusSharedKeyCredentialBuilder.java
   3). sdk/identity/azure-identity/src/test/java/com/azure/identity/ServiceBusSharedKeyCredentialTest.java
   4). sdk/identity/azure-identity/src/main/java/com/azure/identity/implementation/util/ValidationUtil.java
3. Add a new validation method validateForSharedAccessKey in the ValidationUtil class to cope with the two parameter setting methods when the Shared Access Key Credential is created.
   a. When sharedAccessSignature != null , the specified sharedAccessSignature can be directly used to create Shared Access Key Credential, so sharedAccessPolicy and shardAccessKey do not require any verification.
   b. When sharedAccessSignature == null, sharedAccessPolicy and shardAccessKey are required for verification.

@jongio, @conniey for notification.

[ghost]

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

[ramya-rao-a]

@hongli19750210 Please see #16465 (comment) for the updated design to be followed for this task

We should re-use the classes AzureSasCredential and AzureNamedKeyCredential from azure-core.

[conniey]

Looks good aside from the CI build failures.

[hemanttanwar]

Could we add test in integration test for receiving or sending message using sas key ?

[check-enforcer]

This pull request is protected by Check Enforcer.

What is Check Enforcer?

Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass.

Why am I getting this message?

You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged.

What should I do now?

If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows:
/check-enforcer evaluate
Typically evaulation only takes a few seconds. If you know that your pull request is not covered by a pipeline and this is expected you can override Check Enforcer using the following command:
/check-enforcer override
Note that using the override command triggers alerts so that follow-up investigations can occur (PRs still need to be approved as normal).

What if I am onboarding a new service?

Often, new services do not have validation pipelines associated with them, in order to bootstrap pipelines for a new service, you can issue the following command as a pull request comment:
/azp run prepare-pipelines
This will run a pipeline that analyzes the source tree and creates the pipelines necessary to build and validate your pull request. Once the pipeline has been created you can trigger the pipeline using the following comment:
/azp run java - [service] - ci

[jongio]

@conniey / @hemanttanwar - Do you need anything else on this?

[srnagar]

Add more details to javadoc on how to obtain named key credential and sas credential for the next method.

[v-hongli1]

According to your comment, fixed in the new version.

[srnagar]

All input validation should happen before performing any operations on the input. Here ServiceBusSharedKeyCredential should not be created until fullyQualifiedNamespace param is validated.

[v-hongli1]

According to your comment, fixed in the new version.

[srnagar]

This overwrites the value set in the previous overload. So, the order of calls to credential() decides which credential is being used. Instead, we should do the validate in build method and throw exception if both are set.

[v-hongli1]

According to your comment, fixed in the new version.