feat: adding "Critical Region"/"Option" and "Break" blocks to sequence diagram

[financelurker]

📑 Summary

This PR adds the capability to use a "Critical Region" with "Option" blocks and a "Break" block within sequence diagrams.

Resolves #3062

📏 Design Decisions

I've just extended the sequence diagram parser and renderer with aligning the implementation to the existing alt-else/opt blocks.

📋 Tasks

Make sure you

• 📖 have read the contribution guidelines
• 💻 have added unit/e2e tests (if appropriate)
• 🔖 targeted develop branch

[financelurker]

Hi @knsv
The failed lint step seems like a common issue in PRs... don't know why that happens.
The failed static analysis / check tests step: It fails with Error: Resource not accessible by integration - is it possible, that this fails because I've added two new e2e tests and the previous snapshots were not found?

And, locally on my machine one e2e test fails: "should render a state with states in it" with Image was 3.1119696969696973% different from saved snapshot with 82156 different pixels. See diff for details: /mermaid/cypress/snapshots/All Integration Specs/diff_output/State-diagram-should-render-a-state-with-states-in-it.diff.png although I haven't changed anything there...

It would be awesome if this change gets into the next release 👌🏻

[knsv]

Agree, we are looking at the linting issues. We will also add a description for the snapshots. A good workflow when creating a PR would be to generate a local baseline before any changes are made and do a check against that baseline after the changes. Sometimes unexpected side-effects happens.

[knsv]

This looks really good! Extra appreciation for you taking the time to add the corresponding documentation and tests! Thanks!