feat(Geo) Construct: Phase 4 - Documentation

[manavgurnani21]

Description of changes:

With the creation of a new L3 Geo vertical within Amplify, the current documentation for Geo features need to be updated to reflect new functionality. The following changes are made to accomplish that goal:

1. Set up Geo - Redesigned

• adding new set up instructions with new DX
• introducing usage of AWS-managed resources through banner with notice of departure from legacy resources (i.e. maps and places)
• set up instructions for custom access permissions and API keys

2. Customize authorization - New Page 🆕

• instructions on setting up access acceptors
• presenting all access actions comptabile with Geo resources

3. Work with maps - Appended ➕

• added new tabs to set up maps (rendering) with API key access (supported with L3 construct)
• retained legacy map configuration with new Legacy Resources tab

4. Configure location search - Redesigned 🔎

• adding new DX for users to set up place indices

5. Work with location search - Appended ➕

• adding new tabs to set up location search (setting up geocoder and search box)
• retained legacy place configurations with new Legacy Resources tab

6. Configure a geofence collection - Redesigned 🔎

• adding new DX for users to set up place indices

7. Use legacy Geo resources - New Page 🆕

• adding set up instructions for provisioning and configuring legacy resources (i.e. L1 map and place constructs)

Related GitHub issue #, if available:

Instructions

If this PR should not be merged upon approval for any reason, please submit as a DRAFT

Which product(s) are affected by this PR (if applicable)?

• amplify-cli
• amplify-ui
• amplify-studio
• amplify-hosting
• amplify-libraries

Which platform(s) are affected by this PR (if applicable)?

• JS
• Swift
• Android
• Flutter
• React Native

Please add the product(s)/platform(s) affected to the PR title

Checks

• Does this PR conform to the styleguide?

• Does this PR include filetypes other than markdown or images? Please add or update unit tests accordingly.

• Are any files being deleted with this PR? If so, have the needed redirects been created?

• Are all links in MDX files using the MDX link syntax rather than HTML link syntax?
  
  ref: MDX: [link](https://docs.amplify.aws/)
  HTML: <a href="https://docs.amplify.aws/">link</a>

When this PR is ready to merge, please check the box below

• Ready to merge

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.