[Test:] azurerm_cdn_profile/azurerm_cdn_endpoint - fix tests due to deprecated sku values by RP

[WodansSon]

Community Note

• Please vote on this PR by adding a 👍 reaction to the original PR to help the community and maintainers prioritize for review
• Please do not leave comments along the lines of "+1", "me too" or "any updates", they generate extra noise for PR followers and do not help prioritize for review

Description

• Updated documentation to Note: sku deprecation(s).
• Updated test cases to migrate from *_Verizon sku's to Standard_Microsoft sku where possible.
• Fixed failing test cases and remove no longer supported test cases due to the support for Standard_Akamai, Standard_Verizon and Premium_Verizon skus being deprecated.
• Removed no longer supported examples due to skus being deprecated.

Referenced Service Bulletin's:

• Migrate workloads on Azure CDN from Edgio (formerly Verizon) before 7 January 2025.
• Azure CDN will be retiring Azure CDN standard from Akamai on 31 October 2023 – transition to another CDN profile to avoid service interruption.

PR Checklist

• I have followed the guidelines in our Contributing Documentation.
• I have checked to ensure there aren't other open Pull Requests for the same update/change.
• I have checked if my changes close any open issues. If so please include appropriate closing keywords below.
• I have updated/added Documentation as required written in a helpful and kind way to assist users that may be unfamiliar with the resource / data source.
• I have used a meaningful PR title to help maintainers and other users understand this change and help prevent duplicate work.
  For example: “resource_name_here - description of change e.g. adding property new_property_name_here”

Changes to existing Resource / Data Source

• I have added an explanation of what my changes do and why I'd like you to include them (This may be covered by linking to an issue above, but may benefit from additional explanation).
• I have written new tests for my resource or datasource changes & updated any relevant documentation.
• I have successfully run tests with my changes locally. If not, please provide details on testing challenges that prevented you running the tests.
• (For changes that include a state migration only). I have manually tested the migration path between relevant versions of the provider.

Testing

• My submission includes Test coverage as described in the Contribution Guide and the tests pass. (if this is not possible for any reason, please include details of why you did or could not add test coverage)

Change Log

Below please provide what should go into the changelog (if anything) conforming to the Changelog Format documented here.

N/A, test/documentation fix only.

This is a (please select all that apply):

• Bug Fix
• New Feature (ie adding a service, resource, or data source)
• Tests
• Enhancement
• Breaking Change

Related Issue(s)

Fixes #0000

Note

If this PR changes meaningfully during the course of review please update the title and description as required.