This workaround works for me and at least gets the site install working. Of c...

This workaround works for me and at least gets the site install working. Of course, the problem with this is that we won't have the actions for breaking locks but it is certainly better than an exception on install. The workaround is just to run drush cim again after install is done.

In the long term, either the settings should track dependencies and the module should handle them, or we should move to config entities where we get dependencies for free. Another thing we could do is hook into entity type creation and add the actions there as well.

For now, this patch helps us avoid the exception. :)