Support custom pretty print configuration for Spin XML

[tmetzke]

User Story (Required on creation)

As an operations engineer, I can replace the default pretty-printing configuration for Spin XML with a custom configuration. This allows me to define XML attributes that are not stripped of content if they consist of whitespace characters only, for example. With that, my XMLs still get pretty printed - which is great for our users - and adhere to XML schemas that enforce that certain elements always have content, even if it is just one whitespace character, for example.

Functional Requirements (Required before implementation)

• I can configure Spin with a custom XSLT file content that is used when pretty-printing XML files, e.g., when setting XML content as a process variable.
• I can use the existing configuration methods to do that, i.e., use a DataFormatConfigurator for DomXmlDataFormat to configure that dataformat's pretty-print configuration.

Technical Requirements (Required before implementation)

• The DomXmlDataFormat allows defining a pretty print configuration.
• The defined configuration is used when pretty-printing XML content.

Limitations of Scope

Hints

Links

• https://jira.camunda.com/browse/SUPPORT-16910

Breakdown

• [x] Adjust Spin branches
• [x] Release Spin versions
• [x] Adjust Platform POMs

Dev2QA handover

• [ ] Does this ticket need a QA test and the testing goals are not clear from the description? Add a Dev2QA handover comment

---

### Pull Requests
-  [ ] https://github.com/camunda/camunda-spin/pull/205
- [ ] https://github.com/camunda/camunda-spin/pull/210
- [ ] https://github.com/camunda/camunda-spin/pull/209
- [ ] https://github.com/camunda/camunda-bpm-platform/pull/3675
- [ ] https://github.com/camunda/camunda-bpm-platform-maintenance/pull/1065
- [ ] https://github.com/camunda/camunda-bpm-platform-maintenance/pull/1066

[mboskamp]

❓ Why don't we backport this to 7.17 too?

[tmetzke]

❓ Why don't we backport this to 7.17 too?

Excellent question, forgot to mention it here 🙂👍 We don't have pretty-print configurability at all in 7.17.x (using Spin 1.14.x). This was introduced with 7.18. Backporting this would require too much effort in Spin. Plus, the customer only needs this in 7.18. Plus, it's a feature, so we usually don't backport this at all but did it here due to customer request.

[mboskamp]

Alright, that makes sense. Ready for merge from my side 👍