[meta] Tasks to deprecate the Olivero theme

Problem/Motivation

Track the steps needed to deprecate extension Olivero. See Remove a core extension and move it to a contributed project of the deprecation policy.

The removal of extension Olivero was approved in #3590816: [policy, no patch] Deprecate Olivero and move to contrib.

All the child issues here, except in the infrastructure project, are "11.5.0 release priority".

Remaining tasks

To find uses of olivero:

    git grep -lwi olivero | grep -v core/themes/olivero/ | grep -v core/assets | grep -v phpstan-baseline | grep -v MAINTAINERS

1. ✅Find someone to maintain the contrib version of the extension. mherchel has agreed to do this.
2. ✅Add the extension to the list of the Upcoming Deprecations.
3. ✅Move integrations implemented by other modules to the extension.
   Create child issues or child meta issues, as needed, to address the following points. Not all points will apply to all extensions.
   • two search blocks in optional config, block.block.olivero_search_form_narrow.yml and block.block.olivero_search_form_narrow.yml See comment #15
   • Move tests to the extension.
     • #3407067: message.js should work with whitespace in empty message wrappers
     • #3614949: Move tests to Olivero, part 1
     • #3614964: Remove install of Olivero from tests
     • #3618256: Adjust tests using olivero_test test module
     • #3618449: Change uses of Olivero in core/tests and core/profiles
     • #3617523: Remove Olivero from comments
     • #3617584: Change tests using Olivero
     • #3622600: Remove remaining uses of Olivero in tests
   • Help #3602358: Change use 'Olivero' in help module
   • For a theme, move theme-specific integration to the theme.
   • Remove the extension from one or more profiles. #3590882: Standard profile should not include Olivero anymore, should provide guidance on how to get started
   • Remove references to the extension from database dumps. #3623927: Remove Olivero from database dumps
   • Remove templates from the extension’s markup.
     • Remove templates from themes that are staying in core, leave them in deprecated themes
     • Keep skipping the template in the stable copies test.
4. ✅Do a thorough search of core for any remaining references to the extension. If references are found, outside of the extension, then create issues to remove the references.
5. ✅Create the contrib project with a stable release, before the alpha version of the major release. Follow the process in Create the contrib project with a stable release for creating the sub tree split.
6. ✅Deprecate the core extension.#3595083: Deprecate the Olivero theme
7. ✅Create an issue, 'Ensure that Olivero does not get special core treatment' in the packages.drupal.org issue queue to ensure that the composer namespace for the contributed project matches the core one after removal. This is to allocate the drupal/olivero Composer namespace to contrib extension rather than the core extension.
8. ✅Update the Deprecated and obsolete extensions