feat(app-headless-cms): add object and DZ renderer settings

[ma-schmidt-de]

Changes

Okay, this is the 2nd iteration of the new feature to expand object and dynamic zone HCMS fields by default. According to @Pavel910's recommendation, I'm using the new renderer settings feature to define an open attribute. If this attribute is set to true, the accordion of the object or dynamic zone field is expanded.

BREAKING CHANGE: none
Closes: #4109

How Has This Been Tested?

Manually, with an in-code content model.

Documentation

We could use this implementation as an example for the section that describes the renderer settings feature.

[ma-schmidt-de]

Testing the no-code content model editor, I saw that my implementation acts as expected. The switch is rendered and a settings object is added to the field's renderer.

Yet, saving the model the CmsUpdateContentModel mutation fails due to the fact, that the default fields Title, Description and Image don't have a settings object attached to their field renderer. Is this a known issue? 🤔

When I create an empty content model and add an object, dynamic zone or arbitrary field it works just fine.

[Pavel910]

Just one little change here and we're good to go.

On the topic of mutation error, the settings should be either undefined, or an object. I will have a look at this right there in your PR, and will push a fix for this, so we expedite merging of this PR.

Thank you!

[Pavel910]

@ma-schmidt-de I pushed a fix for that issue with existing fields, so settings will always fall back to {} if they don't exist on the field.

[ma-schmidt-de]

@Pavel910 thanks for adding the fix! I polished the code style according to your feedback.
This looks complete to me now. 👍

[Pavel910]

It's approved, let's wait for CI to finish, and we'll merge it then.

[Pavel910]

Thanks @ma-schmidt-de for your contribution! Looking forward to more of these!! 🚀