Updated the LocalizedMapView enum to reflect the addition of the US view

[stevemunk]

Data Plane API Specification Update Pull Request

🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨
Updated the LocalizedMapView enum to reflect the addition of the US view, as per @faterceros

Updated in specification/maps/data-plane/Common/preview/1.0/common.json

This enum is referenced by the following Azure Maps Services/versions:

Render: v1.0, v2022-08-01, v2024-04-01
Search: v1.0

🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨

PR review workflow diagram

Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

API Info: The Basics

Most of the information about your service should be captured in the issue that serves as your API Spec engagement record.

• Link to API Spec engagement record issue:

Is this review for (select one):

• a private preview
• a public preview
• GA release

Change Scope

^{This section will help us focus on the specific parts of your API that are new or have been modified.
Please share a link to the design document for the new APIs, a link to the previous API Spec document (if applicable), and the root paths that have been updated.}

• Design Document:
• Previous API Spec Doc:
• Updated paths:

Viewing API changes

For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures

If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
Swagger-Suppression-Process
to get approval.

Release planner

A release plan should have been created. If not, please create one as it will help guide you through the REST API and SDK creation process.

❔Got questions? Need additional info?? We are here to help!

Contact us!

The Azure API Review Board is dedicated to helping you create amazing APIs. You can read about our mission and learn more about our process on our wiki.

• 💬 Teams Channel
• 💌 email

Click here for links to tools, specs, guidelines & other good stuff

Tooling

• Open API validation tools were run on this PR. Go here to see how to fix errors
• Spectral Linting

Guidelines & Specifications

• Azure REST API Guidelines
• OpenAPI Style Guidelines
• Azure Breaking Change Policy

Helpful Links

• Schedule a data plane REST API spec review

Getting help

• First, please carefully read through this PR description, from top to bottom.
• If you don't have permissions to remove or add labels to the PR, request write access per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories
• To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
• For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
  and https://aka.ms/ci-fix.
• If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
  This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
• If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

[openapi-pipeline-app]

Next Steps to Merge

Next steps that must be taken to merge this PR:

• ❌ This PR has at least one change violating Azure versioning policy (label: VersioningReviewRequired).
  To unblock this PR, either a) introduce a new API version with these changes instead of modifying an existing API version, or b) follow the process at aka.ms/brch.
• ❌ The required check named Swagger BreakingChange has failed. To unblock this PR, follow the process at aka.ms/brch.

[openapi-pipeline-app]

PR validation pipeline started successfully. If there is ApiView generated, it will be updated in this comment.

[github-actions]

API Change Check

APIView identified API level changes in this PR and created the following API reviews

Language	API Review for Package
Swagger	AsyncBatchManagement

[faterceros]

Changes requested to accommodate for US View - Label changes to "Gulf of Ameria" for US View Only._

[FarazGIS]

@Azure/api-stewardship-board @allenjzhang @mario-guerra Could you please review the PR? Thanks!

[mikekistler]

This PR requires review/approval of the deviation from Azure Versioning Policy. Pls come to the next Breaking Changes Office hours to discuss. Normally these are Mondays at 10-11 AM, but are cancelled next week due to the US holiday, so the next office hours will be Monday 6/2. You can also email the Azure Breaking Change reviewers to explain why the Versioning policy is not being followed, or if you need an explanation for why the PR was flagged as non-compliant.

[faterceros]

@Azure/api-stewardship-board @mikekistler
The Version policy is not being followed because the "[Global [Readiness]

https://msit.powerbi.com/groups/me/apps/3abfab4e-307a-4ebf-afaa-6b867bca2d70/reports/5180ca13-1780-438f-990e-5dacfe092767/ReportSection?ctid=72f988bf-86f1-41af-91ab-2d7cd011db47&experience=power-bi&filter=new_geographicissues%2FIntegerID%20eq%2069

The executive order " requirement to add a new Geopol view across all productscame in from GlobalReadiness (CELA) in response to political events in the United States immediately. This includes 'Auto' detection in old versions of the API and making it available across the full product as fast as possible. The US-View fall under these CELA guidelines. Additionally, this does not change the type/fields returned in the response only specific values. It will not break old clients. @FarazGIS