Improve UX of initCollapsed

[codeflorist]

In my opinion the current behaviour of initCollapsed results in a rather bad user experience.

The desired behaviour of collapsed states of blocks or array items regarding a good UX is pretty clear to me:

1. When creating a new item, an editor wants it to be not collapsed on creation, since of course one wants to fill in its fields. So setting initCollapsed to true is rather annoying in this case.
2. When editing a record with possibly a large amount of - maybe even deeply nested - block- and array-items, an editor wants everything to be uncollapsed, since he quickly wants to find the block he wants to edit. Having initCollapsed to false causes the whole page to be a chaotic mess, severely hindering the editor in even finding the element he wants to edit.

Because of (2), the only viable setting for me here is to use initCollapsed: true everywhere, which again results in (1) to be problematic.

Furthermore, currently Payload seems to remember (on the server or db), the collapsed state of every single row. I think this is a very bad idea. After a while each record will become a mess of collapsed / uncollapsed rows and blocks, requiring an editor to "clean up" the page on start or end of an edit session. It's the equivalent of coming back to an untidy and chaotic work desk. It also makes the initCollapsed setting rather useless after a while, irritating developers as to why it is "not working". This has also been requested in this discussion, which got quite a few upvotes: #1376

My suggestions for improvement are:

1. Allow initCollapsed to be an object with { create: boolean, edit: boolean} or a string called auto, which results in the behaviour explained above, and in my opinion should also be the default to provide a good UX out of the box.
2. Remove server/db side saving of collapsed states or (even better) move it into a session-cookie, so it's only saved for the current edit session.