[META] Remove use case specific elements from Standard and Node module. Always install with Standard. Keep Minimal for CLI use only.

Problem/Motivation

This issue is to execute #3159848: [Policy] Always install Drupal with Standard on the UI, pared down of use case specific elements (content types, node listing, commenting, theme), reasons explained there.

Steps to reproduce

Proposed resolution

• 🟢 on main and 11.x already #3587118: Remove content types from the standard install profile and recipe
• 🟡 on main already but in discussion whether to backport to 11.x: #3526560: Mark Umami as hidden in preparation of moving to contrib and/or a testing profile
• 🟡 on main already but backport not yet committed to 11.x: #3588274: Remove Tags vocabulary from Standard profile and recipe
• 🟢 on main and 11.x already #3588276: Remove comment module dependency from standard profile and recipe
• 🟡 on main already but in discussion whether to backport to 11.x: #3520028: Remove support for selecting install profiles via the UI installer -- which was a better solution than #3590801: Mark the minimal profile hidden in the UI (developers can still install with drush)
• To land still on main first: #3590882: Standard profile should not include Olivero anymore, should provide guidance on how to get started. Later on #3595082: [meta] Tasks to deprecate the Olivero theme but that is not in scope of this issue as Olivero would be out of Standard by then.

Not in the Standard profile but a "Standard" behaviour that we want to change even for "Minimal" sites. Unfortunately must be done before Olivero is not enabled anymore, so this is the current highest priority.

• To land still: #3572350: Disable the default /node listing view, replace Olivero hardcoded welcome page from /node with welcome message

Remaining tasks

Open a followup discussion about the future of the minimal install profile / recipe which will be hidden from the UI at least following this issue, but still available.

User interface changes

• A regular Drupal install will not prompt you for an install profile selection anymore.
• The default Drupal experience resulting from this install will not have assumptions about your use case (content types, commenting setup, node listing, frontend theme).
• Instead the default Drupal frontend experience will be suggesting next steps to pick a theme based on your use case. A compelling backend setup will be provided to configure the site on the UI (without assumptions of the use case that you need to undo).

Introduced terminology

API changes

Data model changes

Release notes snippet