Intermediate Inbound Connectors need to be activated for all running process instances

[johnBgood]

Describe the Bug

Currently, Inbound Connectors are activated only for the latest version of each process definition.

This is incorrect, see this discussion.

The customer had a process running in different versions:

• V1, this instance was blocked on a Polling Connector (because we didn't start any connector for this process version)
• V3, working instances

Steps to Reproduce

1. Create a new BPMN diagram, using an Intermediate Polling connector
2. Configure the connector's activation condition so that it blocks there (body.status = "Awesome!NOTCOMPLETED", if your endpoint returns a body with {status: "Awesome!"})
3. Deploy (V1), and start the process
4. Make some changes and deploy+start (V2)
5. Change the response body (use beeceptor) to "Awesome!NOTCOMPLETED"
6. The V1 instance doesn't complete because the connector is not activated anymore

Expected Behavior

Connectors are activated if they're part of a running process instance.

See https://jira.camunda.com/browse/SUPPORT-23440

[sbuettner]

Related: https://github.com/camunda/operate/issues/6415