Migrate to new Zeebe Endpoint APIs (for deploy and run)

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

The Camunda Modeler (Zeebe Tabs) offers the option to “deploy” or “run” (start instance) of a Zeebe process using the “Deploy and run” modal menues.

With the 1.0.0 the Zeebe Broker APIs will change (in particular: workflow will be renamed to process). Hence the “Deploy and run” feature will not work anymore. (This can be tested using the 1.0.0-alpha3 release of Zeebe Broker or later).

Describe the solution you’d like

• Update to a later version of https://github.com/camunda-community-hub/zeebe-client-node-js which supports the new 1.0.0 broker API endpoints.
• Release this change on 11.05.2021 (together with Zeebe 1.0.0 stable).
• Document that Camunda-Modeler v4.8.0 (tbd) supports only Zeebe 1.0.0+ for deploy and run features

Describe alternatives you’ve considered

n/a

Additional context

cc. @menski cc. @jwulf. @jwulf , as far as I understood the to be used zeebe-node-js version would be based on the JS (not the native gRPC) implementation right? Because otherwise, we would run into problems (because of Electron incompatability, we so far were not able to use the native gRPC implementation)

[nikku]

Expected, as this is a breaking change (i believe workflow got renamed to process).

We could consider to catch these incompatibilities. As we’ve discussed we’ll only support Camunda Cloud / Zeebe 1.0 and upwards in the Camunda Modeler.

[barmac]

I’ve just tested Zeebe 1.0.0-alpha.3 together with zeebe-node@1.0.0-alpha.3 and was able to deploy and run without trouble.