* feat: add activiti-core-dependencies-tests module

* revert: set activiti-build.version to 7.0.41

* Update .mergify.yml

* fix: enforce same parent version dependency

* fix: add -DenforceFail=false property to control enforce fail behavior

Refs https://github.com/Activiti/Activiti/issues/2206

* Fixed missing processInstanceId property in SequenceFlowTakenEvent

* Fixed missing processInstanceId property in VariableCreated event

* Clean connectos from previous changes

* fix(version): update org.activiti.core.common:activiti-core-common-dependencies to 7.0.21

* Add missing import

* fix: SequenceFlowImpl => BPMNSequenceFlowImpl

* fix: import file added

* fix(version): update org.activiti.core.common:activiti-core-common-dependencies to 7.0.19

* Trigger CI pipelines

* trigger another CI buld

* trigger build

* fix(version): update org.activiti.build:activiti-parent to 7.0.41

* fix groovy dependency which is missing from SB 2.1

* replace containsExactly for isEqualTo

* Trigger process deployed events

The events will be sent when the Spring Boot application is ready (ApplicationReadyEvent). A ProcessDeployedEvent will be triggered for every process deployed every time the application starts. Listeners to these events should be able do deal with duplicates.

Refs https://github.com/Activiti/Activiti/issues/2149

* Fix transitive dependencies

* Fix integration test

events coming from `WebEnvironment.MOCK` are ignored. So we need to use MOCK here.

Fixes #2167

* Create .mergify.yml

* use squash to merge

Use ResourcePatternResolver.CLASSPATH_ALL_URL_PREFIX: this fix the issue about processes not getting deployed during tests when they are located under src/main/resources/processes

* reproduce the db error and capture with test

* need cleanup of processes as well as tasks now

Instead of listening to the generic internal ENTITY_UPDATED event we are going to explicitly trigger TASK_UPDATED event when TaskRuntime.update is called. That means that no event is going to be triggered if the task is updated outside of the api (directly from TaskService for instance)

* provide a way to copy process vars into task

* tests passing now

* add test at new api level

* will let updatebot handle api version change

* rebase and port to new test approach

* remove unused imports as per codacy