Support zeebe 1.1 clusters by bumping zeebe-node

🚧 This issue is WIP 🚧

Is your feature request related to a problem? Please describe.

Context At the moment the Camunda Cloud infrastructure is creating a DNS entry in the format ${UUID}.zeebe.camunda.io for every Zeebe cluster. This is the unique address the cluster is available at for the user to connect to.

• This limits the amount of clusters we can address to 3.500
• This requires users to wait for DNS propagation

Solution approach by the cloud team: use a single DNS address per region and provide cluster UUID using the :authority pseudo header.

What this means for us

(As of now) the assumption is that zeebe-node-js will be released in a new version which supports zeebe 1.0 and zeebe 1.1.

Based on that assumption, we would need to update to that latest version and ensure everything still works as expected.

Describe alternatives you’ve considered

Integrate two versions of zeebe-node-js (We can not do that)

Additional context

RfC: https://docs.google.com/document/d/1FvTVcSFLactlF0Mw1npq19O-iir4QHzNpzIj4Fzk9S0/edit#

[barmac]

@jwulf is working on a new version of zeebe-node which should support Zeebe 1.1 without any API changes. We will get a status update on Monday.

[barmac]

Since zeebe-node@1.4.0 is out, we can test that.