fix: Improve model property visualization.

[userwiths]

Description

Writing out the schemes seems quite tangled. Here we aim to clear a bit the visualization of array properties.

Motivation and Context

Fixes: #3954

How Has This Been Tested?

Manually, using the default declaration.

Screenshots (if appropriate):

Fully expanded model in the request section:

Fully expanded model in the models section:

Checklist

My PR contains...

• No code changes (src/ is unmodified: changes to documentation, CI, metadata, etc.)
• Dependency changes (any modification to dependencies in package.json)
• Bug fixes (non-breaking change which fixes an issue)
• Improvements (misc. changes to existing features)
• Features (non-breaking change which adds functionality)

My changes...

• are breaking changes to a public API (config options, System API, major UI change, etc).
• are breaking changes to a private API (Redux, component props, utility functions, etc.).
• are breaking changes to a developer API (npm script behavior changes, new dev system dependencies, etc).
• are not breaking changes.

Documentation

• My changes do not require a change to the project documentation.
• My changes require a change to the project documentation.
• If yes to above: I have updated the documentation accordingly.

Automated tests

No tests till now seem to be testing this visualization. If im wrong or if you think we need to make this testable, let me know and I will see what can be done.

• My changes can not or do not need to be tested.
• My changes can and should be tested by unit and/or integration tests.
• If yes to above: I have added tests to cover my changes.
• If yes to above: I have taken care to cover edge cases in my tests.
• All new and existing tests passed.