Regenerate Track 2 KeyVault libraries with new separated 7.1 specs

[daviwil]

This change regenerates the Track 2 KeyVault data plane libraries with the new 7.1 specs that have been separated so that individual services have their own Swagger files. I've also added AutoRest configuration files and npm scripts so that it's easy for anyone to regenerate these in the future.

It appears that there have been some slight changes to the keys.json spec that makes the generated code incompatible with the convenience layer:

src/cryptographyClient.ts:66:7 - error TS2322: Type 'import("/home/daviwil/tmp/keyvault/azure-sdk-for-js/sdk/keyvault/keyvault-keys/src/core/models/index").JsonWebKey' is not assignable to type 'import("/home/daviwil/tmp/keyvault/azure-sdk-for-js/sdk/keyvault/keyvault-keys/src/keysModels").JsonWebKey'.
  Types of property 'kty' are incompatible.
    Type '"EC" | "EC-HSM" | "RSA" | "RSA-HSM" | "oct" | "oct-HSM" | undefined' is not assignable to type '"EC" | "EC-HSM" | "RSA" | "RSA-HSM" | "oct" | undefined'.
      Type '"oct-HSM"' is not assignable to type '"EC" | "EC-HSM" | "RSA" | "RSA-HSM" | "oct" | undefined'.

66       return key.key!;
         ~~~~~~~~~~~~~~~~

src/index.ts:1135:7 - error TS2322: Type 'import("/home/daviwil/tmp/keyvault/azure-sdk-for-js/sdk/keyvault/keyvault-keys/src/core/models/index").JsonWebKey | undefined' is not assignable to type 'import("/home/daviwil/tmp/keyvault/azure-sdk-for-js/sdk/keyvault/keyvault-keys/src/keysModels").JsonWebKey | undefined'.
  Type 'import("/home/daviwil/tmp/keyvault/azure-sdk-for-js/sdk/keyvault/keyvault-keys/src/core/models/index").JsonWebKey' is not assignable to type 'import("/home/daviwil/tmp/keyvault/azure-sdk-for-js/sdk/keyvault/keyvault-keys/src/keysModels").JsonWebKey'.

1135       key: keyBundle.key,
           ~~~

  src/keysModels.ts:148:3
    148   key?: JsonWebKey;
          ~~~
    The expected type comes from property 'key' which is declared here on type 'KeyVaultKey & DeletedKey'

src/index.ts:1138:7 - error TS2322: Type 'string[] | undefined' is not assignable to type 'KeyOperation[] | undefined'.
  Type 'string[]' is not assignable to type 'KeyOperation[]'.
    Type 'string' is not assignable to type 'KeyOperation'.

1138       keyOperations: keyBundle.key ? keyBundle.key.keyOps : undefined,
           ~~~~~~~~~~~~~

  src/keysModels.ts:166:3
    166   keyOperations?: KeyOperation[];
          ~~~~~~~~~~~~~
    The expected type comes from property 'keyOperations' which is declared here on type 'KeyVaultKey & DeletedKey'

src/index.ts:1139:7 - error TS2322: Type '"EC" | "EC-HSM" | "RSA" | "RSA-HSM" | "oct" | "oct-HSM" | undefined' is not assignable to type '"EC" | "EC-HSM" | "RSA" | "RSA-HSM" | "oct" | undefined'.
  Type '"oct-HSM"' is not assignable to type '"EC" | "EC-HSM" | "RSA" | "RSA-HSM" | "oct" | undefined'.

1139       keyType: keyBundle.key ? keyBundle.key.kty : undefined,
           ~~~~~~~

  src/keysModels.ts:162:3
    162   keyType?: KeyType;
          ~~~~~~~
    The expected type comes from property 'keyType' which is declared here on type 'KeyVaultKey & DeletedKey'

Marking this as DRAFT until the requisite spec files have been merged into the azure-rest-api-specs repo (PR Azure/azure-rest-api-specs#8301).

[heaths]

If I'm parsing the errors right in your comment, these are expected until the convenience layer is updated, since "oct-hsm" and "import" enum values were added. Was that all?

[heaths]

I reviewed the smaller diffs in full, and sampled the larger commits - all deletions as expected. Looks good.

[daviwil]

Adding @jonathandturner to spot-check the type coercions I added in commit 7319251 😄

[sadasant]

woah!! Is this all that is needed to regenerate this?

[daviwil]

In theory, yes! I would certainly appreciate if you could clone the branch and give it a shot just to make sure.

[sadasant]

I'm trying it now!

[sadasant]

It says No input files provided. Am I missing something?

[daviwil]

Forgot to commit the swagger/README.md files, fixed now :/

[sadasant]

thank you! It works well!

[sadasant]

The diff of this file is messy. I'm guessing we're now sorting the methods differently? I want to understand. Is this expected?

[daviwil]

It's expected because we're removing a large number of functions from this file which are no longer part of the spec used for @azure/keyvault-certificates The order of functions is the same, I think Git just can't figure out the proper way to diff them since the overall file structure has a lot of overlap.

[sadasant]

Got it! Thank you! This PR works well!

[sadasant]

Looks good! And runs good as well, locally.

[daviwil]

I've regenerated everything here in response to the final spec changes in #7299. If tests go green after the latest CI run, I'll merge it.

Thanks all!