1. if there is a connection error the connection error toast does not show. The connection just has the error icon on top of it.
2. in the single connection world the connect form is pre-populated with the connection if there is a connection error. Should we do that with the connection modal (and show it) in the multiple connections world? That would probably aid in debugging connection errors.
3. if the connection string is invalid (ie. not a connection error) it just silently fails / does nothing. In the single connection world it reports the connection error and we have a test for it. If we pre-populate the connect modal with the connection string and open it the error would show up there.
4. if the connections file is invalid it silently fails. In the single connections world we show an error and we have a test for it.

The auto-connect code that doesn't show a toast (most importantly on connection error) is kinda another version of the same bug from last week: it is another place where we call connect() directly, skipping the code around it thats in the sidebar. In the multiple connections world we need the toast so you can access the error. In the single connection world it didn't matter because the connect form would be in the page and the error would already be visible.