Remove need for explicit definition of client actions [Upgrade to GLSP 2.0]

[rsoika]

See: eclipse-glsp/glsp-server@v1.0.0...v2.0.0

GLSP-1117: Remove need for explicit definition of client actions

Refactor the base GLSP protocol to allow the client to tell the server which actions it is going to handle i.e. which actions should be forwarded to the client

• Add clientActions array to InitializeClientSessionParams. This means the client now has to pass the action kinds it wants to handle as part of the initalize request
• Refactor ClientSessionManager API directly use the InitializeClientSessionParams object for creating new sessions. This means that the ClientSessionManager can also access the generic args properties that might have been passed with the initialize request.
• Replace ClientActionHandler with ClientActionForwader a separate component that is not part of the server-side action handlers.
• Remove configureClientActions method from DiagramModule as the explicit configuration is no longer needed
• Refactor ClientIdModule to ClietnSessionModule responsible for injection session specific configuration like the clientId and the clientActions

What does this mean for Open-BPMN:

In the old version we used the method

 @Override
    protected void configureClientActions(MultiBinding<Action> binding) {
        super.configureClientActions(binding);
        binding.add(BPMNPropertyPanelUpdateAction.class);
    }

in the BPMNDiagramModule to tell the client which kind of actions we send.
Our BPMNPropertyPanelUpdateAction is send by the server in case of complex updates of the property panel. The goal is to tell the property Panel that it must init a complete new layout procedure. For example adding a new Event or Diagram Definition. This situation needs a complete panel update on the client

How to solve?

Currently we have no information about this - see eclipse-glsp/glsp#1150