Geocode the address attribute if it's present

[TimBroddin]

Fixes Automattic/wp-calypso#74281

Proposed changes:

In an old version of the Map block, there was support for having an address attribute. Having this would geocode this address and place a point on the map. This would only happen in the editor.

This PR adds support for this old behavior.

There's a pitfall. You can delete the point, but the next time you edit the page again it will reappear. This seems to be the behavior that's also present in Mapbox. I'm leaving it as is, because this attribute has been deprecated and a workaround would take some time.

Other information:

• Have you written new tests for your changes, if applicable?
• Have you checked the E2E test CI results, and verified that your changes do not break them?
• Have you tested your changes on WordPress.com, if applicable (if so, you'll see a generated comment below with a script to run)?

Jetpack product discussion

Does this pull request change what data or activity we track or use?

No

Testing instructions:

1. Apply this PR
2. Add a new page or post
3. Make sure Mapkit is forced by setting the cookie and reloading: document.cookie = "map_provider=mapkit; path=/;"
4. Switch to code editor and add this code. Note the address.
5. It should add a marker in Brussels

<!-- wp:jetpack/map {"address": "Brussels, Belgium", "mapCenter":{"lat":37.7577,"lng":-122.43759999999999}} -->
<div class="wp-block-jetpack-map" data-map-style="default" data-map-details="true" data-points="[]" data-zoom="13" data-map-center="{&quot;lat&quot;:37.7577,&quot;lng&quot;:-122.43759999999999}" data-marker-color="red" data-show-fullscreen-button="true"></div>
<!-- /wp:jetpack/map -->

[github-actions]

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

• ✅ Include a description of your PR changes.
  
• ✅ All commits were linted before commit.
  
• ✅ Add a "[Status]" label (In Progress, Needs Team Review, ...).
  
• ✅ Add testing instructions.
  
• ✅ Specify whether this PR includes any changes to data or privacy.
  
• ✅ Add changelog entries to affected projects
  

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖

---

The e2e test report can be found here. Please note that it can take a few minutes after the e2e tests checks are complete for the report to be available.

---

Once your PR is ready for review, check one last time that all required checks (other than "Required review") appearing at the bottom of this PR are passing or skipped.
Then, add the "[Status] Needs Team review" label and ask someone from your team review the code.
Once you’ve done so, switch to the "[Status] Needs Review" label; someone from Jetpack Crew will then review this PR and merge it to be included in the next Jetpack release.

---

Jetpack plugin:

• Next scheduled release: April 4, 2023.
• Scheduled code freeze: March 28, 2023.

[github-actions]

Are you an Automattician? You can now test your Pull Request on WordPress.com. On your sandbox, run

bin/jetpack-downloader test jetpack add/map-block-mapkit-address-attribute

to get started. More details: p9dueE-5Nn-p2

[mashikag]

The changes look fine, and the snippet provided does indeed create a map block with a marker set in Brussels.