docs(MVUX): Warn user to not use ItemClickCommand on ListView at the same time as Selection

[DevTKSS]

GitHub Issue (If applicable): closes #

PR Type

What kind of change does this PR introduce?

• Documentation content changes

What is the current behavior?

As not introduced into this important detail so far, we may assume that both callbacks (ListState.Selection & ListView.ItemClickCommand) are invoked if we bind them to the Model, but by setting the ItemClickCommand of the FeedView, our ListState does maybe not longer execute both, the callback from Selection(...) Operator and the command

What is the new behavior?

Added this information to the Mvux Selection Docs where we are introduced into the how to use this Method on the ListState, so users can now know about it and avoid this szenario

PR Checklist

Please check if your PR fulfills the following requirements:

• Tested code with current supported SDKs
• Docs have been added/updated which fit documentation template. (for bug fixes / features)
• Unit Tests and/or UI Tests for the changes have been added (for bug fixes / features) (if applicable)
• Wasm UI Tests are not showing unexpected any differences. Validate PR Screenshots Compare Test Run results.
• Contains NO breaking changes
• Updated the Release Notes
• Associated with an issue (GitHub or internal)

Other information

If we should instead expect both of them to be executed if set, then please fix this instead!

Internal Issue (If applicable):

[Copilot]

Pull Request Overview

This PR updates the Selection.md documentation file by fixing the YAML front matter formatting and adding new warning and note sections about ListView selection behavior and GitHub links.

Key changes:

• Corrected the YAML front matter delimiter formatting
• Added a warning about ItemClickCommand interfering with the Selection operator
• Updated GitHub sample repository links to include more descriptive text

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.