[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

• ✅ but under backport to Drupal 11: #3587118: Remove content types from the standard install profile and recipe
• ✅ #3526560: Mark Umami as hidden in preparation of moving to contrib and/or a testing profile
• #3588274: Remove tags vocabulary from standard profile and recipe
• #3588276: Remove comment module dependency from standard profile and recipe
• #3590801: Mark the minimal profile hidden in the UI (developers can still install with drush)
• #3590882: Don't enable the Olivero theme by default in the Standard profile/recipe and potentially later: #3590816: [policy, no patch] Deprecate Olivero and move to contrib

Not in the Standard profile but a "Standard" behaviour that we want to change even for "Minimal" sites:

• #3572350: Disable the default /node listing view and add a better default front page for new installs

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