Closes #5425 Add carousel categories

[joshuasosa]

Description

Adds carousel categories with a new carousel categories taxonomy, categories field in the carousel content type, category contextual filter in the carousel view, and adjusts the paragraphs view to enable carousel as an option.

The idea is to use a flexible block to add a paragraph view with the argument filled for a certain category. That block can then be placed in the highlight block region and restricted to a certain page or set of pages.

Release notes

Adds categories for Quickstart Carousel Item. To use, create a flexible block with a view element and select the AZ Carousel view. Expand open options and set the argument to the desired carousel category. The block can then be placed in the highlight area in block layout and set to display on a certain page or set of pages.

Related issues

Closes #5425

How to test

Types of changes

Arizona Quickstart (install profile, custom modules, custom theme)

• Patch release changes
  • Bug fix
  • Accessibility, performance, or security improvement
  • Critical institutional link or brand change
  • Adding experimental module
  • Update experimental module
• Minor release changes
  • New feature
  • Breaking or visual change to existing behavior
  • Upgrade experimental module to stable
  • Enable existing module by default or database update
  • Non-critical brand change
  • New internal API or API improvement with backwards compatibility
  • Risky or disruptive cleanup to comply with coding standards
  • High-risk or disruptive change (requires upgrade path, risks regression, etc.)
• Other or unknown
  • Other or unknown

Drupal core

• Patch release changes
  • Security update
  • Patch level release (non-security bug-fix release)
  • Patch removal that's no longer necessary
• Minor release changes
  • Major or minor level update
• Other or unknown
  • Other or unknown

Drupal contrib projects

• Patch release changes
  • Security update
  • Patch or minor level update
  • Add new module
  • Patch removal that's no longer necessary
• Minor release changes
  • Major level update
• Other or unknown
  • Other or unknown

Checklist

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.
• My change requires release notes.

[accesswatch]

Draft accessibility note — category field is fine, one heads-up for the filtering UI

The category taxonomy field and vocabulary config look good — options_select for the edit form gives a standard labeled <select> element, and hiding the field in the view display is correct since filtering happens via URL argument. Nothing here changes the front-end carousel rendering.

One thing to keep in mind when building the filtering UI:

When tab bars, button groups, or links are eventually added to let users filter the carousel by category, those controls will need proper ARIA patterns:

• A group of filter buttons should use role="group" with a group label (e.g. aria-label="Filter by category")
• The active/selected filter needs aria-pressed="true" (toggle buttons) or aria-current="true" (links)
• If filtering updates the carousel without a full page load, a live region should announce the result count change (same pattern raised in Issue/3998 Sub-Branch: Add Results Count and Full Pager to Trellis Opportunity Importer #5506)

Not a concern for this PR as-is — just flagging it early so the pattern is designed in from the start rather than retrofitted.