Add a link to the Status report warning about obsolete extensions so site owners can fix the problem

Problem/Motivation

If you have a site with an obsolete extension that is still installed, the status report currently says:

Obsolete extensions found: %extensions. Obsolete extensions are provided only so that they can be uninstalled cleanly. You should immediately uninstall these extensions since they may be removed in a future release.

#3266308: %extensions placeholder not extension names printed on the Status report warning about obsolete extensions will fix the bug that the %extensions placeholder isn't getting the values replaced. But it leaves the problem that site owners won't necessarily know how to fix this problem and silence the warning.

Steps to reproduce

1. Start with a Drupal core 9.4.x test site
2. Create a new module test and install it, you can use the following .info.yml file:
   

   name: 'Test module'
   type: module
   description: 'Test module'
   package: Testing
   version: VERSION
   core_version_requirement: ^8 || ^9
     

3. Go to /admin/modules and install the module
4. Change the info file and add the lifecycle obsolete:
   

   lifecycle: obsolete
   lifecycle_link: 'https://example.com/obsolete'
   

5. Rebuild the cache
6. Go to admin/reports/status and check the warnings

Proposed resolution

Convert the words "uninstall these extensions" into a link to the Uninstall form at /admin/modules/uninstall.

Remaining tasks

1. Decide if we need to be fancy about if it's only an obsolete theme (?!?) or if it's cool to always link to the modules Uninstall form.
2. Land #3266308: %extensions placeholder not extension names printed on the Status report warning about obsolete extensions
3. Add the link
4. Update test coverage
5. Reviews/refinements
6. RTBC

User interface changes

The warning on the status report when a site has an obsolete extension installed includes the words "uninstall these extensions" which is now a link to the Uninstall page at /admin/modules/uninstall.

Before

After

API changes

None.

Data model changes

None.

Release notes snippet

TBD, probably not.