Spring Boot integration dependency issues

Describe the bug
I'm focusing on the BPMN process engine since that's what I'm most familiar with. There are multiple conceptual problems with the Spring Boot integration that every user of the integration would sooner or later hit:

1. Even though you've taken care of starting the async executor later so that all beans (mainly JavaDelegates and FlowableEventListeners) are already loaded, this is still a problem for direct usages of RuntimeService#startProcessInstance* during startup. The reason is the same - there's an implicit requirement that all beans are loaded before using a given process definition.
2. The same consideration mentioned above has to be applied on shutdown. Otherwise, a given JavaDelegate bean can be destroyed before the async executor is shut down and the process instances may fail due to the absence of the bean in the application context.

Expected behavior
The above problems and necessary considerations should be clear to anyone trying to use the integration as well as having proper and flexible solutions to the problems (especially the second one).

Additional context
Flowable version: 7.0.0.M1, Spring Boot integration. Database: Postgres 14.

Beginne damit, den Spring Boot-Integrationslebenszyklus rund um RuntimeService#startProcessInstance* und den asynchronen Executor während des Anwendungsstarts und -shutdowns nachzuverfolgen. Vergleiche die Reihenfolge der Bean-Initialisierung und -Zerstörung und definiere anschließend Tests oder Lebenszyklusprüfungen, die zeigen, dass Delegates und Event Listener verfügbar bleiben, bis die Prozessarbeit abgeschlossen ist.