Add (hopefully failing) unit test checking if baseline values from
multiple bar plots will interfere and delete each other.
Change Domainer.paddingExceptions to be managed by key, so that Plots
can register their exceptions with their own ID to make sure that
the exception is not erroneously removed by another plot's deregistration.

Do the same for includedValues.

To maintain backcompat and make it simple for otehrs to add padding exceptions,
if you add an exception without a key, it can't be removed.
Have AbstractBarPlot make "BAR_PLOT+ID" be the key for the domainer registration,
to reduce the probability of accidental collisions with the user's exceptions.
Merge branch 'master' into domainer-registration

Conflicts:
	plottable.js
Merge branch 'master' into domainer-registration

Conflicts:
	plottable.js
	src/components/plots/abstractBarPlot.ts
Update AreaPlot to use the domainer registration logic
Make the domainer-areaplot-exception tests more robust, by having them be
independent of the domainer implementation
Change paddingExceptions and includedValues in domainer so that they can be
added and removed without a key.

Implemented via overloaded typesignatures (boolean or string are valid
parameter types)
Change API for exceptions and included values:

- addPaddingException(value, key?)
- removePaddingException(valueOrKey)

- addIncludedValue(value, key?)
- removeIncludedValue(valueOrKey)
Merge branch 'master' into domainer-registration

Conflicts:
	test/rendererTests.ts
	test/tests.js
Merge pull request #621 from palantir/domainer-registration

Domainer registration