Remote storage onboarding section improvements

[shcheklein]

• If storage of a specific type is detected we should activate the relevant tab automatically (e.g. Azure one)
• Should we collapse the whole section if the storage is set already? similar to the way we do with the DVC section
• Modify action. I should always see and have a way to get to the config file. Similar to how let's say Jest config page works - it has a link to the settings.json. The reason there is that we don't cover all the needed fields to manage it.
• Display remote information in the sidebar (similar to the strategy and reasoning for the Studio "tree") - this could potentially also display whether or not the remote is up to date with data and have a refresh button to check on the status.
• Enable quickstart with some kind of provided storage option (depends on https://github.com/iterative/studio/issues/6223)

[mattseddon]

Can we combine this with the remaining items in #3867? I.e move the remaining items into this issue (or drop them) and close that one.

[shcheklein]

Yes, absolutely, I forgot that it was still open tbh.