Deprecate geo location module

[monsieur-z]

Fixes https://github.com/Automattic/vulcan/issues/604

Proposed changes:

This PR removes the geolocation module from the Jetpack plugin and adds a deprecation warning for the Jetpack_Geo_Location class.

The feature enables users to tag posts with geolocation data (in Calypso) and include the information in RSS feeds, meta tags, and Geo microformat following post content.

Initially tackled in this PR: #40895. This PR keeps the includes to prevent potential fatals, as hinted here: #40895 (comment)

Given the scope of the feature, no deprecation warning is issued.

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

n/a

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

No.

Testing instructions:

Note: I haven't been able to tag posts with geolocation data in Calypso. Let's at least verify the PR doesn't break posts and that deprecation warnings are issued.

• Spin up a Jetpack test site with this branch
• Install and activate a theme that supports geo-location, such as Twenty Seventeen
• Make sure you can see your server logs
• Open your browser console
• Create a new post, publish it, and visit the frontend
• Check there's no errors in the console or the logs
• Check that you can see the deprecate warning in the server logs
• Install the Twenty Four theme
• Notice you don't see the warnings

[github-actions]

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

• To test on WoA, go to the Plugins menu on a WordPress.com Simple site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin, and enable the remove/remove/jetpack-geo-location-2 branch.

• To test on Simple, run the following command on your sandbox:

  bin/jetpack-downloader test jetpack remove/remove/jetpack-geo-location-2
  

Interested in more tips and information?

• In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
• Read more about our development workflow here: PCYsg-eg0-p2
• Figure out when your changes will be shipped to customers here: PCYsg-eg5-p2

[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.
  
• ✅ Add a "[Status]" label (In Progress, Needs Team Review, ...).
  
• ✅ Add a "[Type]" label (Bug, Enhancement, Janitorial, Task).
  
• ✅ 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.

---

Follow this PR Review Process:

1. Ensure all required checks appearing at the bottom of this PR are passing.
2. Choose a review path based on your changes:
   • A. Team Review: add the "[Status] Needs Team Review" label
     • For most changes, including minor cross-team impacts.
     • Example: Updating a team-specific component or a small change to a shared library.
   • B. Crew Review: add the "[Status] Needs Review" label
     • For significant changes to core functionality.
     • Example: Major updates to a shared library or complex features.
   • C. Both: Start with Team, then request Crew
     • For complex changes or when you need extra confidence.
     • Example: Refactor affecting multiple systems.
3. Get at least one approval before merging.

Still unsure? Reach out in #jetpack-developers for guidance!

---

Jetpack plugin:

The Jetpack plugin has different release cadences depending on the platform:

• WordPress.com Simple releases happen semi-continuously (PCYsg-Jjm-p2).
• WoA releases happen weekly.
• Releases to self-hosted sites happen monthly. The next release is scheduled for February 4, 2025 (scheduled code freeze on February 4, 2025).

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

[monsieur-z]

Only show the deprecation warning if the theme supports the feature.

[coder-karen]

This tests well for me, just left a typo fix suggestion 👍