fix: #3626669 Let the Admin role do its work: permissions, sign-in and listings

Issue: https://www.drupal.org/project/cucumber_core/issues/3626669

A member of the Admin role could not write a feature: the Gherkin script field was closed and no role held a step of the automated testing workflow. Anonymous visitors met an access denied page with no way to sign in.

• Grant the Admin role the Gherkin text format, the steps of the workflow and the media, taxonomy and media directories permissions the Feature form needs, in a recipe of its own. No permission that administers the site.
• Require and install Anonymous Redirect, in place of the settings that were imported without the module. The pages of a password reset stay open, and a one-time log in link leads to the account form.
• Name the steps of the workflow after where they lead, add the way back to Draft, and make To Do, In Progress and Implemented current revisions, so the listings show the state a feature was moved to.
• The Features page asks for "access features page", lists every feature, finds a feature by a part of its name and has no "Insert selected" button.
• Let the admin dashboard depend on the views it shows, so its Features listing is there from the install on.
• Print the links at the foot of the dashboard listings with a Views area of this module and its own styles, for the people who may follow them.
• Say when a listing is empty, and drop a key of the date formatter that has no configuration schema.
• Import the image styles and the Media Directories browsers in the foundation recipe, so a site built from a recipe has them.
• Update functions bring installed sites to the same configuration, and a post update makes the newest revision of a feature the current one.

AI-Generated: Yes