[2467] Add connected elements tool to the General View

[AxelRICHARD]

Expose existing elements connected to the selected element through both inbound and outbound General View relationships.

Add the tool icon and integration coverage.

Bug: #2467

PLEASE READ ALL ITEMS AND CHECK ONLY RELEVANT CHECKBOXES BELOW

Auto review

• Have you reviewed this PR? Please do a first quick review, It is very useful to detect typos and missing copyrights, check comments, check your code... The reviewer will thank you for that :)

Project management

• Has the pull request been added to the relevant milestone?
• Have the priority: and pr: labels been added to the pull request? (In case of doubt, start with the labels priority: low and pr: to review later)
• Have the relevant issues been added to the pull request?
• Have the relevant labels been added to the issues? (area:, type:)
• Have the relevant issues been added to the same project milestone as the pull request?

Changelog and release notes

• Has the CHANGELOG.adoc + doc/content/modules/user-manual/pages/release-notes/YYYY.MM.0.adoc been updated to reference the relevant issues?
• Have the relevant API breaks been described in the CHANGELOG.adoc?
• Are the new / upgraded dependencies mentioned in the relevant section of the CHANGELOG.adoc?
• In case of a change with a visual impact, are there any screenshots in the doc/content/modules/user-manual/pages/release-notes/YYYY.MM.0.adoc?
• In case of a key change, has the change been added to Key highlights section in doc/content/modules/user-manual/pages/release-notes/YYYY.MM.0.adoc?

Documentation

• Have you included an update of the documentation in your pull request? Please ask yourself if an update (installation manual, user manual, developer manual...) is needed and add one accordingly.

Tests

• Is the code properly tested? Any pull request (fix, enhancement or new feature) should come with a test (or several). It could be unit tests, integration tests or cypress tests depending on the context. Only doc and releng pull request do not need for tests.

[cbrun]

Following our discussion, the tool now excludes connected elements that can be represented as ports or inside a compartment/container of any selected node, even when the compartment is hidden. This uses the node descriptions rather than a blacklist of semantic types. Independent connected elements are still exposed, and existing representations are preserved.

Added unit and integration coverage, including single and multiple selections. The local build passes, and all coverage thresholds are met.

[AxelRICHARD]

That's much better indeed 👍
Just few comments and it will be ok, thank you!

[cbrun]

@AxelRICHARD Thanks for the review! Both remaining comments are addressed in e11f9b2. Local Maven validation/Checkstyle, commit-message tests and all metadata checks pass.

Do you prefer keeping the individual commits as they are, or would you like me to squash them once the review is complete, before merging?

[AxelRICHARD]

I'll rebase, squash and merge it myself, thank you!