Migrate to MPS 2024.1.1

[alexanderpann]

• fixes Update to MPS 2024.1 #918

Nothing special changed. I only had issues with icon loading for plugin models that are nested in other models. Those models couldn't be opened in the logical view. The workaround seems to be to set Generate initializer config to true in the StandalonePluginDescriptor. The changes related to introducing the XML stubs are related to mbeddr. We need them available in MPS-Extensions since we depend in the batik stubs on then.

Note: We skipped MPS 2023.3 on purpose and decided to immediately go to MPS 2024.1.

Encountered known MPS issues:

• https://youtrack.jetbrains.com/issue/MPS-36888/java.lang.UnsupportedOperationException-not-implemented
• https://youtrack.jetbrains.com/issues/MPS?q=java.lang.IllegalStateException:%20Write%20actions%20are%20prohibited
• https://youtrack.jetbrains.com/issue/MPS-37823/Invalidate-caches-and-restart-Failed-to-close-and-dispose-all-projects
• https://youtrack.jetbrains.com/issue/MPS-37533/idea.log-DisposalException-on-MPS-shutdown

Other non-migration-related issues:

• SubDiagram example not loading anymore #1003
• java.lang.RuntimeException: 2 applicable implementations found for de.q60.mps.explorer.pf.TraceBuilders_base.buildTrace(EditorCell_Collection [EditorCell_Collection]) #1004

[sergej-koscejev]

• LineNumberComponent#install: the editor component disposed check should come even before trying to retrieve the project from the component.
• MyConnectPreview, MyGraphComponent: getActionUpdateThread() is only the thread that actions will be updated on, they will still be executed in EDT. Since update is empty, it could be done on BGT because this is preferred.

Requesting changes because XML jars need to be dowloaded with Gradle, not checked into Git.

[sergej-koscejev]

Please squash/fixup the commits that add and remove jars, so that we don't have the jars in Git history after merge.

[sergej-koscejev]

I fixed up the commits and force-pushed the branch.

[sergej-koscejev]

I am merging the MPS and JBR version update separately in #1010, so that we don't build a 9999.9 version from the 2024.1 branch.

Jar changes were implemented

[alexanderpann]

@sergej-koscejev Is there anything else that needs to be done, or can this PR be merged now?

[sergej-koscejev]

I want to understand why we need those resolver and serializer jars that come from this new Maven repository. Can we get rid of them?

[alexanderpann]

I guess you have to check the history in mbeddr why they were introduced: https://github.com/mbeddr/mbeddr.core/tree/master/code/languages/com.mbeddr.mpsutil/solutions/org.xml/lib
As mentioned privately before, the XML serializer is used by IETS3.

One use case at least is the batik language in mbeddr.core: https://github.com/mbeddr/mbeddr.core/tree/master/code/languages/com.mbeddr.mpsutil/solutions/org.apache.batik
I really would love to not touch those JARs anymore. If you remove the wrong one, the diagrams won't load. We had multiple classloading issues with this language in the past. The last time they broke was with the migration to 2023.2.

The new maven repo is really unfortunate but I couldn't find a better source.