For many frontend editors, the Category List view is the central place to browse, edit, and create articles. In busy categories (or on sites with many authors), that list can become overwhelming because it shows all articles.

This PR introduces an optional author filter for Category List and Category Blog menu items—aligned with the author filtering options already available in mod_articles for consistency. The result is a cleaner frontend management experience: less noise, faster scrolling/searching, and a lower risk of accidentally editing the wrong item—especially on multi-author sites. It also enables “special” views such as Articles by a specific user or Your personal news.

Summary of Changes

• Add mod_articles-style author filtering options (Include / Exclude / Current User) to Category List and Category Blog menu item parameters.
• When Current User is selected, hide the author selector and limit the output to the logged-in user’s articles.
• Pass the author filter state through CategoryModel to the Articles model, and remove unintended alias filtering / unrelated version-bump changes.

Testing Instructions

1. Edit a Category List menu item:
   • Set Author Filtering Type to Include or Exclude and select one or more authors.
   • Switch to Current User and confirm the author selector is hidden.
2. View the menu item in the frontend while logged in:
   • With Current User, verify only the logged-in user’s articles are shown.
   • With Include/Exclude, verify the selected authors are respected.
3. Repeat the same checks for a Category Blog menu item.

Actual Result (Before This PR)

• The Category List displays all articles in the selected category.
• There is no option to filter the list to the currently logged-in user’s own articles.

Expected Result (After This PR)

• Author filtering matches mod_articles: Include / Exclude / Current User.
• Current User hides the selector and limits results to the logged-in author.
• No unintended alias filtering and no unrelated version edits.

Documentation

I’m happy to provide documentation and screenshots once the feature is approved/accepted.