Label and Image styling and class name updates

* copied widgets.css from 0.5 distribution
* made js files match
* fixed some actualSize config in old test files
Updating unit tests to new css names
Updated multiple choice code to match 0.5 behavior

* multiplechoicequestion.js will overwrite feedback so only one div appears
* updated to use new stylenames and styles
* updated button class names
* fixed unit tests to match
Indicated tests necessary for writing and overwriting feedback div
ABC Mortar defined, skeleton Hilite mortar class created, both added to build
Started image unit tests
Initial implementation of Hilite mortar along w/ ILightable interface

w/ unit tests
NeffReactor: update the activity config and create new hilite mortar by hand

Added mortar config to the activity config that is using the manually derived eventIds. These are the same topics as are used in the manual creation of the mortar and should allow for the enhancement of the BricLayer to create the mortar.
Updated to brixBarChart class
- changed class names
- fixed selector to do highlighting (no comma, wrong order of selectors)
swapping in maxSize property to svg container
Manza Highlightable Bar Chart demo
- new ManzaHealth.html page
- css fixup for highlighting
- scaling in barchart lite function
- extra question in the activity database
started BricLayer support for mortar
briclayer supports creating mortar, NeffReactor built completely by briclayer

briclayer unit tests for mortar now pass
briclayer (and bric) support for reporting topics (event ids) is still needed before the 350 hilite mortar story is complete.
fix image unit tests, including adding a workaround for chrome bug to the helper.js
internal feedback class was potentially interfering w/ MCQ prev feedback removal

Copied over changes from last updates in NeffOctDemo branch.
minor cleanup-formatting & comments AND fix for chrome bug

This fix from the NeffOctDemo branch:
quick fix: 981 unable to submit MC questions on Chrome Mac & Windows

After the Chrome update of 10/3/2013 it seems element.querySelector is working as though the element was the document root and not considering the element itself or it's ancestors when evaluating a selector match.
This caused no input elements to be selected to have changed event handlers set.
Fixup css, and a better test image
- css update
Revert "Fixup css, and a better test image"

This reverts commit 9ef35616bcf8f9a33aef594c1cb6c817d1659656.
Merge branch 'origin/0.5port'

 test image"

This reverts commit 9ef35616bcf8f9a33aef594c1cb6c817d1659656.
Merge pull request #99 from lbondaryk/0.5port

0.5port