Review existing KeyVault CI failures

• LintDiff failure:

The operation 'CreateCertificate' returns 202 status code, which indicates a long running operation, please enable 'x-ms-long-running-operation.","code":"LongRunningOperationsWithLongRunningExtension"

See here the recommendation.

• GoSDK CodeGen Faulure:

It seems Go CodeGen is failing for composite swagger, this seems due to mismatch definitions of same parameter "vaultBaseUrl " in two different swagger listed in the composite section

cmderr [generator automation] [AUTOREST] FATAL: Error: '$["x-ms-parameterized-host"].parameters' has incompatible values (---
cmderr [generator automation] [AUTOREST] - name: vaultBaseUrl
cmderr [generator automation] [AUTOREST] description: 'The vault name, for example https://myvault.vault.azure.net.'
cmderr [generator automation] [AUTOREST] required: true
cmderr [generator automation] [AUTOREST] type: string
cmderr [generator automation] [AUTOREST] in: path
cmderr [generator automation] [AUTOREST] x-ms-skip-url-encoding: true
cmderr [generator automation] [AUTOREST] , ---
cmderr [generator automation] [AUTOREST] - name: vaultBaseUrl
cmderr [generator automation] [AUTOREST] description: 'The vault name, for example https://myhsmvault.managedhsm.azure.net.'
cmderr [generator automation] [AUTOREST] required: true
cmderr [generator automation] [AUTOREST] type: string
cmderr [generator automation] [AUTOREST] in: path

Start with the KeyVault composite configuration in specification/keyvault/data-plane/readme.go.md and review the linked OpenAPI authoring guideline for the CreateCertificate response. Reproduce the LintDiff and Go CodeGen checks, then verify that the long-running-operation metadata and composite parameter definitions no longer cause either failure.