Use only BFF from UI

[b-rowan]

Refactors UI and BFF to not require any use of API from the UI. BFF is basically a copy of API for now (except for the GET methods).

Also some misc JS fixes, and an added router for uploading firmware. Uploading firmware is now combined into 1 endpoint in both the API and BFF.

Closes #81, Closes #91

[tsagadar]

Commit f674a68 : either rewrite commit message (detail: no "." at the end of the first line) or ideally split in two (needs some git voodoo skills that pay off over time - or a good IDE).

[easybe]

Commit f674a68 : either rewrite commit message (detail: no "." at the end of the first line) or ideally split in two (needs some git voodoo skills that pay off over time - or a good IDE).

Yes, that commit looks like a squash gone wrong. Better split it up if the 2 changes are unrelated.

This can be done with interactive rebase:

1. git rebase -i origin/master
2. Change first line to:

   e f674a68 # This is a combination of 2 commits. # This is the 1st commit message:
   

3. Save & quit
4. git reset HEAD^ (or only extract some file(s) and amend)
5. Redo the two commits
6. git rebase --continue

Concerning the commit message quality, there has been quite some progress 🙏. To take it one step further, I would appreciate if we could agree to follow the very common conventions outlined here, i.e.:

Summarize changes in around 50 characters (no period here)

More detailed explanatory text, if necessary. Wrap it to about 72
characters or so. In some contexts, the first line is treated as the
subject of the commit and the rest of the text as the body. The
blank line separating the summary from the body is critical (unless
you omit the body entirely); various tools like `log`, `shortlog`
and `rebase` can get confused if you run the two together.

Explain the problem that this commit is solving. Focus on why you
are making this change as opposed to how (the code explains that).
Are there side effects or other unintuitive consequences of this
change? Here's the place to explain them.

Further paragraphs come after blank lines.

 - Bullet points are okay, too

 - Typically a hyphen or asterisk is used for the bullet, preceded
   by a single space, with blank lines in between, but conventions
   vary here

If you use an issue tracker, put references to them at the bottom,
like this:

Closes: #123

[b-rowan]

Yes, that commit looks like a squash gone wrong. Better split it up if the 2 changes are unrelated.

Yeah, should be fixed now. I think they are related closely enough to be 1 commit (hence the failed squash).