Improve the logging/noticing of Legacy REST API usages

[Konamiman]

Changes proposed in this Pull Request:

This pull request expands on #40535, #40866 and #41804 by adding the following improvements:

• Add the IP address of the requester to the generated log entries.

• Replace the "an extension will be available" text with "an extension is available", including a link to the extension in the WordPress.org plugins directory, in the usages detected notices and in the Legacy REST API settings page notices:

How to test the changes in this Pull Request:

First, if you have tested the pull requests mentioned above, you'll probably have dismissed the relevant notices; you'll need to undo the dismissals first:

wp user meta delete <your user id> "dismissed_legacy_api_usages_detected_notice"
wp user meta delete <your user id> "dismissed_legacy_api_removed_in_woo_90_notice"
wp user meta delete <your user id> "dismissed_legacy_webhooks_unsupported_in_woo_90_notice"

If you have the separate Legacy REST API extension installed, you need to at least disable (or uninstall if you prefer) it.

Make sure to have the Legacy REST API activated in settings, and to have webhooks that depend on the Legacy REST API (see the testing instructions in the other pull requests welcome); and force the recreation of the notices: wp eval 'WC_Admin_Notices::reset_admin_notices();'

Now go to the Legacy REST API settings page, you should see three Legacy REST API warnings (two dismissable notices, and one paragraph under the setting, as in the screenshot above); verify that all the links in those work as expected.

Finally, repeat the testing instructions of #41804 and verify that the log entries contain the IP address of the requester.

Changelog entry

• Automatically create a changelog entry from the details below.

Significance

• Patch
• Minor
• Major

Type

• Fix - Fixes an existing bug
• Add - Adds functionality
• Update - Update existing functionality
• Dev - Development related task
• Tweak - A minor adjustment to the codebase
• Performance - Address performance issues
• Enhancement - Improvement to existing functionality

Message

Improve the logging/noticing of Legacy REST API usages

Comment

[github-actions]

Hi @lsinger,

Apart from reviewing the code changes, please make sure to review the testing instructions as well.

You can follow this guide to find out what good testing instructions should look like:
https://github.com/woocommerce/woocommerce/wiki/Writing-high-quality-testing-instructions

[github-actions]

Test Results Summary

Commit SHA: db80f0d

Test 🧪	Passed ✅	Failed 🚨	Broken 🚧	Skipped ⏭️	Unknown ❔	Total 📊	Duration ⏱️
API Tests	259	0	0	2	0	261	0m 39s
E2E Tests	173	0	0	114	0	287	5m 20s

---

To view the full API test report, click here.
To view the full E2E test report, click here.
To view all test reports, visit the WooCommerce Test Reports Dashboard.

[lsinger]

Closing and re-opening to trigger the CI checks.

[lsinger]

This tests as intended -- the notices appear with correct links and the IP address is added to the logs.

I left two comments, one of which I think we should address (the sanitization one), but I'm open to arguments against as well.

[lsinger]

Thanks for addressing my comments -- still tests well and I have no further comments.