feat: #3621521 Add the author page as a view with its banner fields

Implements #3621521.

What changed

• views.view.rightup_author_articles at author/%user, listing one author's published articles ten to a page through vartheme_bs5_rightup:views-view-unformatted and the impressed_card_medium view mode.
• An author_banner user view mode plus two user fields, field_author_role and field_author_bio, added to the profile form and the profile page beside the picture.

Access is perm / access content, caching is tag, the pager is explicit, and there is an empty area so an author who has published nothing still gets their banner.

Why a view and not an entity view mode

Canvas content templates are node only on this build - any other entity type is rejected with "The value you selected is not a valid choice" - and the user entity has no biography or role field to render. The design's author page is a banner followed by the same listing the landing page carries, so a view with a contextual filter fits it better anyway.

Two things a reviewer will ask about

The header area sets bypass_access: true. The author_banner view mode renders only those two editorial fields, so it carries nothing private. The alternative was granting anonymous users access user profiles, which varbase_users_base deliberately scopes to authenticated users - that would have reversed an upstream decision and opened every profile page rather than these two fields.

The view mode is declared as a config dependency by hand. Views does not trace a plugin option, so its own dependency calculation drops the view_mode the entity header area names, and the recipe could install the view before the view mode exists.

Known gap

The page has no h1 yet. Core's ViewPageController::getTitle() builds the view without setting arguments or executing it, so an argument-derived title can never reach a views page route, and user.name is not display-configurable. The heading therefore needs a theme change, which is not in this MR.

Verification and provenance

Verified on a Varbase 11 install of this recipe on a local site whose vartheme_bs5_rightup is a working-copy checkout with uncommitted changes. That proves the configuration, not that the branch applies against the canonical theme, so it is stated rather than left for a reviewer to discover. Every component this branch references was checked to exist in canonical vartheme_bs5_rightup at 5dd414e.

No clean-apply regression run against a canonical theme yet, so that checkpoint is unticked.

Checkpoints

• File an issue about this project
• Addition/Change/Update/Fix to this project
• Testing to ensure no regression
• Automated unit/functional testing coverage
• Developer Documentation support on feature change/addition
• User Guide Documentation support on feature change/addition
• UX/UI designer responsibilities
• Accessibility and Readability
• Reviewed by a human
• Code review by maintainers
• Full testing and approval
• Credit contributors
• Review with the product owner
• Update Release Notes
• Release

AI-Generated: Yes