After updating RCP client target from 4.17 to 4.24 the BindingService manager can't be initialized

Question

After updating client target from 4.17 to 4.24 I am getting an exception in the Workbench on line 2247. This is happening after calling PlatformUI.createAndRunWorkbench(display, advisor);

        StartupThreading.runWithoutExceptions(new StartupRunnable() {

            @Override
            public void runWithException() {
                BindingManager.DEBUG = Policy.DEBUG_KEY_BINDINGS;
                bindingManager = e4Context.get(BindingManager.class);
                bindingService[0] = ContextInjectionFactory.make(BindingService.class, e4Context); // Throws an exception
            }
        });

The error I get is 'org.eclipse.e4.core.di.InjectionException: Unable to process "BindingService.manager": no actual value was found for the argument "BindingManager"' and the application cannot start.

There was a similiar problem here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=400265 and making the BindingManager optional was a solution, I wonder if I could make it optional in BindinService somehow.

Is there any way to force the BindingManager to be loaded and/or set so the application starts?