Initial KeyVaultAccessControlClient for Java

[vcolin7]

Tests and samples are still pending and the README is a work in progress.

Based on issue: #8007.

[JimSuplizio]

There's a tag that needs to be updated in the README that I called out but otherwise the EngSys items in here are fine. I trust you to update the tag so I'll pre-approve this from an EngSys perspective.

[heaths]

Some parameter names different from other languages, but we can unify on those for beta 2. Same for a few getters I pointed out.

[heaths]

These are required parameters for create methods. Are they being passed to those methods directly as well?

[vcolin7]

These parameters are passed directly to the service methods.

This Properties object is based on how the service Swagger groups parameters, however, I believe we certainly could change the method signature to take all required values like this:

public Mono<KeyVaultRoleAssignment> createRoleAssignment(
    KeyVaultRoleAssignmentScope roleScope,
    String roleDefinitionId,
    String principalId)

Instead of what we have today:

public Mono<KeyVaultRoleAssignment> createRoleAssignment(
    KeyVaultRoleAssignmentScope scope,
    KeyVaultRoleAssignmentProperties properties)

What do you think @heaths?

[heaths]

I thought we were doing it that way in .NET after a discussion, but I don't see that in source. @christothes and @sadasant, was it a different method we were talking about pulling roleDefinitionId and principalId out of, or was that for the model constructor? I may just be remembering wrong here.

[christothes]

I think we still use a properties bag in .NET, but I like the individual parameter shape better.