feat(deployment): use last endpoint deployed for all files

[azeghers]

In accordance with https://github.com/bpmn-io/internal-docs/issues/224, this PR aligns the Zeebe Modeler deployment plugin with the Camunda Modeler one.

Which issue does this PR address?

Closes #227

Acceptance Criteria

• [ ] Corresponds to the concept
• [ ] Corresponds to the design

Definition of Done

• [ ] corresponds to the design principles
• [ ] corresponds to the code standards
• [ ] passes Continuous Integration checks
• [ ] available as feature branch on GitHub
  • [ ] contains the cleaned up commit history
  • [ ] commit messages satisfy our commit message guidelines
  • [ ] a single commit closes the issue via Closes #issuenr

[azeghers]

Small finding, the test covering this section only tests with a single saved endpoint, which wasn't very useful back when the deployment tool could handle multiple endpoints. The test is now appropriate without modification.

[pinussilvestrus]

Just to understand it correctly: We ignore the multi-endpoint concept for now and use the same endpoint globally for every file, right? Because this is what I experienced when trying it out

• Create a deployment for diagram1.bpmn --> endpointA is saved
• Open deployment modal for diagram2.bpmn --> already existing endpointA is used as default
• Modifiy the endpoint configuration for diagram2.bpmn --> endpointA is updated
• Open deployment modal diagram1.bpmn --> modified endpointA is used

And so on. So basically there is currently only one global endpoint being used for all diagrams. Is this the intended behavior?

It's actually the same in Camunda Modeler, so I guess the answer is "yes" 😄

[azeghers]

@pinussilvestrus That's correct.

[pinussilvestrus]

Works well for me 👍 Just some thoughts for possible code changes.