The JUnit API documents assertEquals as taking the expected argument
before the actual argument.  Failure to adhere to this can result in
very confusing test failure messages.

For example in testTransformOneValue 'old' contains 'A' and 'expected'
contains 'a'.  If the implementer does not lower-case the key, the
failure message is as follows if the argument order is
(actual, expected):

EtlTest > testTransformOneValue FAILED
    java.lang.AssertionError: expected:<{A=1}> but was:<{a=1}>
        at org.junit.Assert.fail(Assert.java:88)
        at org.junit.Assert.failNotEquals(Assert.java:834)
        at org.junit.Assert.assertEquals(Assert.java:118)
        at org.junit.Assert.assertEquals(Assert.java:144)
        at EtlTest.testTransformOneValue(EtlTest.java:27)

This is very confusing as "was:<{a=1}>" is exactly what we were hoping
the result would be.

* remove Guava and use JUnit assert

* reassign old to Collection.unmodifiable

* reassign variable expected

- in journey test, remove @Ignores so that test runs exercise all tests.
- increase the verbosity of test logging to aide in seeing progress as
  tests are un@Ignored and solved.
- saving scripts used to make changes to all exercises.  These are the
  start of a library of scripts making such changes easier.
- make Gradle output more CI-friendly.

With exercism/exercism.io@54e1df3, we can now gather exercises into a
subdirectory. By separating the language track files from the
configuration and management files, it is easier to read the project.

- move gradle config under "exercises" too as it would make a mess
  otherwise.

Use Guava in the tests to make it easier to build up
maps needed for testing the API.