[2391] Add support of inheritance of actor in actors compartment

[jerome-obeo]

Add support of inheritance of actor in actors compartment of CaseDefinition and CaseUsage graphical nodes
The actors compartment is also visible in the following graphical nodes:

• RequirementDefinition
• RequireUsage
• ConcernDefinition
• ConcernUsage
• SatisfyRequirementUsage

Bug: #2391

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.

[AxelRICHARD]

This comment makes me feel we do something wrong here.
It seems strange to have several way of instantiation for inherited item node descriptions.
Please take the time to check if they could/should be instantiated the same way for every inherited item node descriptions.

[jerome-obeo]

Actually, actors compartment node provider for RequirementDefinition and RequirementUsage was made twice (as the item node provider):

• a first time explicitly in actors compartments creation method with a dedicated provider (handling custom label for compartment name).
• a second time in compartments general creation method (createCompartmentsForListItems) because actorParameter reference was in global map COMPARTMENTS_WITH_LIST_ITEMS with a generic code.

The second provider was never read due to cache provider retrieval method that only returns the first node provider with a given name.
I decided to remove the references SysmlPackage.eINSTANCE.getRequirementUsage_ActorParameter() and SysmlPackage.eINSTANCE.getRequirementDefinition_ActorParameter() from the global map COMPARTMENTS_WITH_LIST_ITEMS.

[AxelRICHARD]

Ok it seems fair. Please be sure that it does not broke anything else. We want to still be able to view those compartments, and be able to create/delete/edit actors inside them.