[meta] Tasks to remove Ban module

Problem/Motivation

Track the steps needed to remove extension Ban from core to contrib. See Remove a core module and move it to a contributed project of the deprecation policy.

The removal of extension Ban was approved in #1570102: [Policy] Deprecate Ban module.

Remaining tasks

1. ✅ Create a child issue, 'Remove Ban from core'. #3571886: Remove Ban from core
2. ✅ Deprecate the extension in the current minor development branch. If the next major branch is open, the extension can be removed via a separate patch (to avoid dependent patches), otherwise an issue should be opened to remove the extension once the next major branch is open.
3. ✅ Open an issue, 'Ensure that Ban 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/Ban Composer namespace to contrib extension rather than the core extension.
4. >✅ Manually test upgrading from the core extension to the contrib extension. There is an issue template available for this.
5. ✅ Triage core issues for Ban in the core queue and move either to the contrib project or the relevant core component. Restore the status to what it was before it was postponed. Also, is the issue moved to contrib, then move any change record.
6. ✅ Move all core documentation for Ban to the contrib project. Make issues in the contrib project to update or add links to the documentation on the project page.
7. ✅ When the issue in https://www.drupal.org/project/project_composer is Fixed update the documentation with the new Composer command.

Release notes snippet