Alphabetize all the things

In order to comply to WCAG 2.0[1], buttons must have discernible text that
clearly describe the purpose, so that it can be used by screen readers.

[1] https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/H65

It doesn't help anything. Doing a deep compare is unnecessary because the underlying components will do the necessary comparison themselves. Simply seeing if the sprite list has changed at all is enough.

With jscodeshift thank God

* Fix costume loading in sprite info pane

Requires LLK/scratch-vm#517

* Fix costume loading in costumes tab

Requires LLK/scratch-vm#517

Remove target pane button and actions

Add back putting the sound library in the ui

Affects SpriteSelector Pane, StageSelector Pane, Stage, MenuBar, Libraries Modal, Add/Import buttons, for Chrome, Ffx + Safari on Sierra.

Fixes #162

Refactored towards better convention for linting.

Very crude, requires a refactor to allow toggling

For the time being, update the position onChange. Eventually this will update onBlur/on "enter" key

* Remove errant conditional logic for backdrop / costume modal. Resolves GH-100
* Remove unused var. Re GH-100

* Stage/Backdrop: design pass. Changed how selected state works to keep width of pane from shifting. Switched to fixed pixel width to match design spec
* SpriteSelector: removed flex basis width. Pane grows to expand the empty space, since Stage is now fixed width
* SpriteInfo: updated to correct dropdown values. Updated 2nd row type sizing and radio box border-radius
* SpriteInfo: made labels non-selectable. StageArea: added border
* SpriteSelectorItem: Updating type size to match SpriteInfo

Configurable SpriteSelectorItems per row (#90). Standardized spacer variable (#84). MenuBar Pass (#130)

* Standardized use of space units where appropriate
* Reversed box classes for easier readability in Inspector
* Sprite Area: removed unused info button
* SpriteSelectorItems: fixed spacing between rows. Isolated layout + component CSS, now reusable in other context. Items per row is now easily configurable
* MenuBar: refactored structure for clickable items

* Covers parts of these issues: GUI layout panes (#69), sprite libraries (#12), import buttons (#64), menu bar (#67), and sprite info area (#53)

~ Refactored layout pane structure by removing `display: flex` from `.box`, by default. Declaring flex instead only where specifically needed. This helped fix layout quirks, and should help us avoid hard to find issues related to nested flex boxes

~ Added descriptive classnames to boxes/containers/wrappers. Moved more padding, margins + layout into these wrappers to help with component reusability.

~ Set up a spacer unit variable inside `gui.css`, to start keeping consistent padding, margins and rounded corners between panes. Used [CSS/PostCSS Modules](https://github.com/css-modules/postcss-modules-values) to avoid SCSS dependency.

~ Refactored inline styles from JSX, into CSS files. 2 reasons: a) prepping for reuse of CSS Module variables. b) Feels easier to debug complex flex layouts when all the styles are in one place vs JS/HTML/CSS syntax mixed together

~ Added menu bar into layout via new component, and sprite info header in sprite selector pane, with stubs for the labels + forms. Sprite items are correctly scrolling, while leaving the header fixed, in Chrome. Mostly working in FFx. Not working in Safari, IE yet.

~ Style pass on library modal

~ Experimenting with a few different transition styles: Logo in menu bar, sprite library items, Add buttons.

Improves performance by comparing sprite info values (rather than object identities), and by excluding irrelevant data from this comparison.

Remove MediaLibrary helper since it is now unused

Move layout styles from component stylesheets to the GUI, or the component that is placing the component.

Add a new `Box` component to control layouts, basically giving a convenient way to lay out with flexbox.

Use `Box` as the output component for any component that may need to be passed layout options. The props passing convention allows giving layout props to the final `Box` component, making wrapping with another `Box` unnecessary in some cases.

It was not being used by GUI so no reason for it to be initialized there

The inline css method gives us nothing that CSS modules can't give us. This puts the project more in line with the way www works, and makes CSS actually readable.

Using class names gives us full control of the modal styles.