Fix: Collections/state consistencies, concurrently dependency

[tzfx]

I went through and did a once through for some of the react components. Most of the issues pertained to:

1. Removed the ...this.state part of this.setState({...this.state, <some changes>}) in a bunch of places. The function does a shallow merge of this.state anyway, and I think it may actually confuse change detection.
2. Moved after-construction init code to onComponentMount in some places to make sure state was actually available at the point at which the function fired off.
3. See the comments/changes around L348 of Collections.tsx... In order to get Tabs to not throw a fit when we were adding/removing collections, I had to do some reacty state-juggling things.
4. Added the key=<some-key> prop for any components that we loop over as required by React.
   • I still need to go through a bunch of the other components and do this so my console doesn't light on fire when I navigate through the application.
5. Added the dev dependency concurrently. With this thing, we can now stand up both the test webserver and the react app all with one command and run them together. Added npm start dev and updated the README.

[jgunzelman88]

Change destination to v0.8.0

[tzfx]

Rebased and retargeted.

[tzfx]

Reverted the version overall app version change (back to 0.8.0) that had come in with me branching off of main/rebasing.