Exclude page row from layout definition in rows with one single element

[apedroferreira]

Duplicates

• I have searched the existing issues

Latest version

• I have tested the latest version

Summary 💡

Right now every element in the layout of a Toolpad application is inside a Row component, even if a row only has one single element inside it.
This makes it so that the layout definition is usually more complex and has a deeper hierarchy than it needs to, especially for isolated elements, which are very common.
These types of Row components can be omitted from the page layout definition and have the Toolpad runtime wrap them automatically in rows, so that the page hierarchy becomes cleaner and easier to read.

Extra (maybe isolate to separate issue in due time): on saving a Toolpad YAML file, make it so that the file is automatically optimized according to this improvement, eliminating single-element rows.

Examples 🌈

No response

Motivation 🔦

On a first implementation of the page hierarchy explorer, it was noticed that every element at the deepest level is shown as being inside a page row, which makes it more cumbersome to work with and does not provide the most useful information as easily.
Fixing this issue would solve this type of problem on the deepest level, without any extra workarounds/inconsistencies being needed for the explorer to be easy to work with.