Update dashboard to design v122 (Part 1)

[somebody1234]

Pull Request Description

• Close Update the Dashboard to Newest Design #9886

  • Update style of buttons in Drive Bar
  • Move "Home" page into a "Start" dialog
  • Remove icons that are no longer needed
  • Remove Backend Switcher in top bar - they have now been converted to categories

• Incidental changes

  • Refactor Backend provider so that both Remote and Local backends are available.
    • This was done because both Cloud and Local backends are now easily accessible by switching tabs - the Local backend no longer has its own views with the hidden category switcher

Important Notes

None

Code review tips

• There are a lot of changes in Settings components, for example (and in general, any component that needs to use a backend). However, most of the changes are identical, so only the approach needs to be reviewed - although the settings pages and the other pages should probably be reviewed separately.

Testing instructions

• Make sure new/changed features work, as mentioned above (drive bar, start page, drag-n-drop)
• Because of the backend changes, all flows in general should be checked, at least at a basic level:
  • Sign up/sign in
  • Offline mode (bottom link on login screen on desktop app)
  • Checking that all settings pages work, both when logged in and not logged in

Screencasts

dashboard-122.mp4

Checklist

Please ensure that the following checklist has been satisfied before submitting the PR:

• The documentation has been updated, if necessary.
• Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
• All code follows the
  Scala,
  Java,
  TypeScript,
  and
  Rust
  style guides. In case you are using a language not listed above, follow the Rust style guide.
• Unit tests have been written where possible.

[somebody1234]

I guess I'll avoid stacking the move to tabs on top of this PR, as this is a big PR so there may be a lot of changes needed.

[somebody1234]

re: 3 - most style issues were fixed in the second PR. i figured it's easier to implement it once rather than having to backport. thoughts?

[somebody1234]

2 & 3. should be addressed.

1. seems like it's a bigger feature, but hopefully it's the last thing to address (after some other final refactors)

[somebody1234]

on second thought 1 will be left for later