Redis track 2 .NET SDK 2022-06-01 API version updates

[austintolani]

Summary
These changes contain the newly generated code for the Azure.ResourceManager.Redis package based on the new 2022-06-01 API version. This generation actually includes new code for changes made in both the 2022-06-01 and 2022-05-01 API versions:

• [Redis Cache] New API Version 2022-06-01 with some extra linked server properties added for server role update/failover support azure-rest-api-specs#20869
• [Hub Generated] [Microsoft.Cache] 2022-05-01 API: Add "Latest" option to "redisVersion" property, async linked server, managed identity changes  azure-rest-api-specs#19506

Testing
I have re-recorded the existing tests using the new API version and added some additional testing coverage.

[archerzz]

There are two types of breaking changes in the new version:

1. Two methods are changed to long running
2. New parameters inserted into the constructor of model class

• For item2, you could write customization codes to provide backward compatible constructors.
• For item1, I think you could also write customization codes to provide backward compatible operation methods. Inside the backward compatible methods, you await on the new long running methods.

I'll leave the decision for you. You could write customization codes to provide backward compatibility. Or you could bump the major version.

[austintolani]

@archerzz I've spoken with my team and we've decided the best approach for us is to bump the major version number. I've updated the version number to 2.0.0 in CHANGELOG.md. Is there anything else that I need to do to? Should I be leaving the date as "(Unreleased)" in CHANGELOG.md?

[archerzz]

@archerzz I've spoked with my team and we've decided the best approach for us is to bump the major version number. I've updated the version number to 2.0.0 in CHANGELOG.md. Is there anything else that I need to do to? Should I be leaving the date as "(Unreleased)" in CHANGELOG.md?

@austintolani

• If it's just an update on the codes and you're not going to release the SDK right now, you can leave it with (Unreleased).
• If you're going to release the SDK, you need to update with the release date.

By the way, the pipeline is broken because the version number in CHANGELOG.md is inconsistent with the value in Azure.ResourceManager.Redis.csproj.

[austintolani]

Thanks @archerzz, I've updated the CHANGELOG accordingly. My plan is to release the SDK. Can we merge the PR?

[austintolani]

@archerzz There is one failing test that seems to be a timeout failure. Are these type of failures common? Is there anything I can do to fix it?

[archerzz]

@archerzz There is one failing test that seems to be a timeout failure. Are these type of failures common? Is there anything I can do to fix it?

No worry. I've restarted the failed job, and it's fine now.

[austintolani]

Awesome, thanks for all your help @archerzz