FE: Messages: Fix stack overflow for large messages

[git-halinka]

• Breaking change? (if so, please describe the impact and migration path for existing application instances)

What changes did you make? (Give an overview)
When viewing large messages in AceEditor I was getting: RangeError: Maximum call stack size exceeded
After some googling, it looks like setting wraperEnabled to false fixes the issue
Additionally, I had to set example:
spring.codec.max-in-memory-size: 15MB -- in config.yml
and
max.request.size: 15000000 on cluster preferences when I wanted to be able to produce large messages

Is there anything you'd like reviewers to focus on?

How Has This Been Tested? (put an "x" (case-sensitive!) next to an item)

• No need to
• Manually (please, describe, if necessary)
• Unit checks
• Integration checks
• Covered by existing automation

Checklist (put an "x" (case-sensitive!) next to all the items, otherwise the build will fail)

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (e.g. ENVIRONMENT VARIABLES)
• My changes generate no new warnings (e.g. Sonar is happy)
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged

Check out Contributing and Code of Conduct

A picture of a cute animal (not mandatory but encouraged)

[Haarolean]

@git-halinka please rebase the PR

[kapybro]

Further user feedback is requested. Please reply within 7 days or we might close the issue.

[kapybro]

Thanks for the additional feedback! We'll get back to your issue soon.

[kapybro]

Further user feedback is requested. Please reply within 7 days or we might close the issue.

[kapybro]

Thanks for the additional feedback! We'll get back to your issue soon.

[Haarolean]

@git-halinka please either:

1. rebase the PR so a fast-forward merge is possible (no other unrelated commits present in main are present in your branch)
2. or check the 'maintainers has access to the PR' on the right side of the PR so we can do this for you

[kapybro]

Further user feedback is requested. Please reply within 7 days or we might close the issue.

[kapybro]

No feedback received within 7 days. Auto closing.