Integrate changes needed for SECURE

[AlexeiQ]

This PR integrates necessary changes for itemis SECURE which were implemented on #2221 and therefore by #2198 by others. I've cherrypicked and updated the necessary commits and ommited all unnecessary/ now irrelevant changes after reviewing all the commits.

❗ The only change where I'm unsure and would like some advice/ additional review is: com.mbeddr.mpsutil.actionsfilter.runtime: Set the solution kind to NONE. (eee1745d)

Changes

• Force Save All and Execute Re-Runnable Migrations on com.mbeddr.core and com.mbeddr.mpsutil

com.mbeddr.mpsutil.editingGuide

• ProgramFragments support error suppression, i.e. all model-checking errors are suppressed in ProgramFragments, so modelchecker will disregard them and not clutter.
• Fragment module depends on its original module, to access data that is needed, but in the original module and not copied to the temporary exercise model (SECA-867).

mpsutil.hyperlink.runtime

• HyperlinkUtil.openInBrowser() behaves like no-op instead of raising an exception on null/empty URLs.

com.mbeddr.mpsutil.asynccell

• Stop polling for the calculated value in case the poll-request throws an exception and show to the user, that the calculation has failed together with the thrown exception, instead of spamming the log on each poll with the exception.

com.mbeddr.mpsutil.actionsfilter.runtime

• Set the solution kind to NONE. The actual reason for this change is not documented unfortunatly. It was probably either a simple clean-up or it caused class-loading issues in a project and therefore was necessary, which at the current time cannot be reproduced/verified anymore.

com.mbeddr.core.base + .../pluginSolution

• Add possibility to explicitly not display roots of concept IMbeddrIDERoot in mbeddr menus.

com.mbeddr.mpsutil.actionsfilter

• Implement missing behavior methods.
• Add error handling for missing actions.

Checklist for creating a good PR (can be deleted)

• [x] I've described my change in the CHANGELOG.md if it is visible to users of the platform (mandatory).
• [x] I've selected the correct base branch.
• [x] I have checked my code (edge cases, no errors) and corrected any misspellings.
• [x] I have added comments to my code in areas where the code is hard to understand.
• [ ] I've created a new language/solution.
  • [ ] I've added the language/solution to the build script (tutorial in readme)
  • [ ] I've added a sandbox that showcases the language.
  • [ ] There is some kind of documentation available in the repository or somewhere else [e.g. MPS Platform Docs].
  • [ ] I've introduced a breaking change.
    • [ ] I've made it clear that a change is breaking e.g. [breaking] prefix in the title
    • [ ] I have written new tests/changed old tests.
    • [ ] I have created migrations when necessary (e.g., deprecation of concepts, properties, enumeration values).
    • [ ] I haven't removed concepts, properties, references, or children without deprecating them first.
    • [ ] I have moved nodes or models by using the refactoring move action.

[AlexeiQ]

Thanks for the review and feedback :)

I assume you tested this change.

No, I did test everything else but the actionsfilter yet. I executed the gradle-command "behind" ./gradlew install, but it didn't rebuilt the module, which is then copied to the MPS plugins directory. I have to do this tomorrow again properly.

[AlexeiQ]

I did test the actionsfilter plugin by now, by calling ./gradlew install and thus installing a new actionsfilter plugin into my MPS (cleaning the build and the plugin-directory beforehand). The actionsfilter is still working properly afai can see and the idea.log is free of any new, releated exceptions. After a discussion with @alexanderpann we agreed to go on with the merge.