Remove the Search module

I think this is unblocked now, but it needs a rebase.

Rebased. Prior fails included stuff in Olivero, do we have a removal order we are going in? If Olivero is removed before this then we don't need to remove search stuff from Olivero.

Also the core_fake database driver still has SearchQuery and ViewsSearchQuery references even with this MR I think.

It looks like we're three issues away from Olivero removal, #3622600: Remove remaining uses of Olivero in tests, the issue to deprecate, and the issue to actually remove, so trying to get those done first to reduce the work here probably makes sense - although the maintenance burden of search is higher than Olivero in general.

Also the core_fake database driver still has SearchQuery and ViewsSearchQuery references even with this MR I think.

Didn't check those but I think we could delete them here too?

Remaining failures all seem to be down to Olivero, so postponing then on removing Olviero: #3595089: Remove the Olivero theme.

Reviewed everything that was not within the search module directory that we're removing entirely. Can't see anything to complain about.

This removal from SchemaCheckTrait mentions #3380475: SearchPage entities implicitly require labels: make explicit, and fix migration from D7:

    'search.page.*' => [
      // @todo Fix config or tweak schema of `type: search.page.*` in
      //   https://drupal.org/i/3380475.
      // @see search.schema.yml
      'label' => [
        'This value should not be blank.',
      ],
    ],

The reference to search.settings in that issue probably needs to be split out to its own issue in the contrib search queue.

Otherwise this looks good, and I can commit later when I'm back at the computer. I'll also re-verify then whether there aren't any search references left to remove after applying the changes.

Committed and pushed 64a266aae44 to main. Thanks!

I did grep for search after removing but there's so many references in things like $search in str_replace that I'm sure we will find tendrils in the future.

Great work all.

I quoted the wrong snippet in #12. I meant this one:

'search.settings' => [
      // @todo Simple config cannot have dependencies on any other config.
      //   Remove this in https://www.drupal.org/project/drupal/issues/3425992.
      'default_page' => [
        "The 'search.page.node_search' config does not exist.",
      ],
    ],

The reference to search.settings is in #3425992: contact.settings, filter.settings, etc. all have dependencies, which violates the basic rule of simple config.

I have created the new issue for Search: #3624588: search.settings has dependencies, which violates the basic rule of simple config.

Just want to note that there was surely (surely?) discussion about the decision to remove Search module from core, but nothing is reflected here. It feels weird to have task-only issues, with no reference to the context of why the task was undertaken, for major things like moving a core module to contrib! I think it would be best practice to link to, or paste into a background section of the module section, some reference to the motivation. (I think i can guess and i agree, but again— strange not to have any reference available from here.)

@mlncn #3476883: [Policy, no patch] Move Search module to contrib is linked from the issue summary of the parent

Added as a related link here.

This turned up while writing Drupal 12 beta release notes: #3627629: Remove search module coverage from robots.txt.