Handle EnumerationIO and EnumerationDeprecatedIO

[zepumph]

From working on renaming in #95

Steps for this issue:

• Both EnumerationDeprecatedIO and "RichEnumerationIO" (soon to be EnumerationIO), will have the type name EnumerationIO.
• Make them share or know about each other's cache, and assert that phetioDocumentation is not different if they share the same type name.
• Look into combining files to see if it makes sense or is possible.

We don't think it will cause complications with PhET-iO to have them share the same name for PhET-iO because each IOType is parametrized on the actual instance of enumeration, so we know the right values will be given by the PhET-iO system.

[zepumph]

• Move this IO type to tandem from axon. It can't be in phet-core because it relies on tandem.

[zepumph]

Alright, with only a limited addition of API in EnumerationDeprecated, I was able to consolidate EnumerationIO types. There is now just a single IOType, in tandem, that both EnumerationDeprecated and Enumeration use. I think that this issue is ready for review by @samreid once everything get's pushed.

[zepumph]

Most important for the review @samreid: will you please make sure that the changes to ts-config files are as expected. I exclusively removed include/exclude paths, but they all seemed like workarounds, so I hope all is well here!

[samreid]

I reviewed all the commits and didn't see any problems. I skimmed the changes in tsconfig files and they seem reasonable. I think tsc would have told us if some file was out of scope. Can this issue be closed?