[Key Vault] Ensure crypto operations work as expected for all API versions

[mccoyp]

Context: the generated KeyOperationResult class only has iv, authentication_tag, and additional_authenticated_data attributes in API versions 7.2+. This isn't usually an issue, since most or all algorithms using these values require symmetric keys -- these can only be used with Managed HSM for now, which only supports API versions 7.2+.

However, some crypto operations that use some of these attributes (AES-CBCPAD, for example) can be performed locally. It's possible that someone would -- for whatever reason -- create a CryptographyClient with an earlier API version than 7.2 and attempt to perform crypto operations that use these attributes. That may not work since the generated models loaded by the CryptographyClient may not have support for the attributes.

To fix this, if it is a problem (which I have reason to think it is), we'll probably want to add a check before performing certain crypto operations -- either when we check that an algorithm is supported by our local crypto provider, or inside the encrypt/decrypt/etc. method.

[github-actions]

Hi @mccoyp, we deeply appreciate your input into this project. Regrettably, this issue has remained inactive for over 2 years, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.

[mccoyp]

We can leave this closed since our generated code structure has since changed (we only generate code for the latest API version).