Restructure Dial-related Components

[SkylerBurger]

As a developer, I want my components to be more reusable and single-purposed in order to more easily control how they render without resorting to a Router.

• [x] Create a <Dialer /> component that will contain both the <DialGroup /> and <GroupTabs /> components.
  • This will make it easier for the tabs to disappear appropriately when we're not viewing the dials directly.
• [x] Capture what is happening in <GroupTabs /> when showSettings is true. Recreate that red closing X element as its own component that can be loaded any time we're viewing a component that can be simply closed.
• [x] Refactor <App /> so the view change from dials to settings still works smoothly.

[SkylerBurger]

Started on #21 and realized there were a lot of state dependencies that controlled rendering of various components at the App level. Grouping these components together into "views" will make it easier to wrangle which component display and when.

[SkylerBurger]

This took a little longer than expected but the refactoring was address in PR #32