Fix path to edoc-info for removal
Neotoma does not order the generated file correctly for edoc, so remove module @doc (and fix formatting for future reinstatement)
Edoc tries to parse < as html tag
Use ordsets in apply_mappings() fold

The fold function in apply_mappings() would simply cons mappings
to lists for either dropping or keeping a mapping, and then
subtracting the two. The effect was, in a sense, a majority vote:
if more mappings than not indicated dropping, the translation
would be dropped, counter-intuitively.

Solution: make the accumulators ordsets instead. Two test cases
were added: one with 1 'good mapping' and 1 'bad', and the other
with 1 'good' and 2 'bad'. The second test failed before the fix.
Fix review problems
Format variables in validation error messages
Add +a emulator flag as erlang.async_threads.stack_size
Decrease the testing time for the builder
Compute friendly sizes for the user so they don't need to know wordsize
Refactor apply_translation into multiple functions.
Code reformatting
Eliminate nested case statement
Remove dead code, enum handling happens in cuttlefish_enum now
WIP fixing re-applying transformations
Add guards to some datatypes that fail on recursive calls
Found source of nested config bugs + extended types

* Tweaked cuttlefish_nested_schema_test to provoke the bug more clearly.
* When transform_extended_type encounters an error, it didn't continue
  processing the list. This means that anything that isn't a string and
  isn't of that type would fail and not try any other types. Now we cons
  the error into the accumulator and continue.
Refactor transform_type so it's not mutually tail-recursive

* Factored out the control flow of transform_type/2 into foldm_either.
  foldm_either/2,3 returns on the first successful transformation and
  otherwise accumulates errors. This means that
  transform_supported_type/2 and transform_extended_type/2 don't have to
  manually call transform_type/2 with the remaining list on failure,
  instead simply returning {ok, V} or {error, Reason}.
* transform_type/2: Since is_supported/1 and is_extended/1 are mutually
  exclusive, I converted the case with tuples into an 'if'. This looks
  cleaner to my eyes.
* transform_supported_type/2: Converted the case with an internal 'catch'
  into a try with pattern-matching. 'catch' has been known to perform
  less well than try/catch and the syntactic result more clearly calls
  out the exceptional case.
Replace string:join/tokens with cuttlefish_variable calls
Use testing_time for the builders
Bump up eunit timeout and use imported functions from eqc