Make translation directory locations modular

[mattjdnv]

Added code to the translationServer to use a hoot config variable for translation directory locations

Adding to hoot-services next. Am trying to have one way to specify translation directories at run time to make deployments easier.

Got rid of the config var and now it searches $HOOT_HOME/translations* looking for translationConfig.json files
This file is a combination of the DefaultTranslations.json file and the TranslationServer config file.

There is a bit of cleanup to do to remove the last of the hardcoded translations-local stuff.
And, as usual, the documentation needs an update as well.

[brianhatchl]

Was it intentional to change the order of the translations in the schema switcher drop down?
was this:

now this:

This change seems like it was intended to "demote" the earlier versions of TDS in importance?

[mattjdnv]

Yes. I did re-order the translation list to put the newer / more popular ones first.

[brianhatchl]

Not sure why this same core test is failing:

Failure: N4hoot19AddressConflateTestE::runTest

src/test/cpp/hoot/core/conflate/address/AddressConflateTest.cpp(185)   - Expected: 21

- Actual  : 28

It seems to pass locally when run in isolation with:

HootTest --single N4hoot19AddressConflateTestE::runTest

[brianhatchl]

Not sure what to do about the test failure

[bmarchant]

This looks like a change that happened with the upgrade of the libpostal library. I'll take a look.

[brianhatchl]

ok, I definitely had not re-provisioned since that update

[bmarchant]

@mattjdnv BLUF: if you merge origin/master into this branch, it should fix that error. (or you can ignore it, merge this PR and everything will be in master and it will be fine.)

Long version: Because libpostal was upgraded in hoot-deps from 1.0 to 1.1 and we weren't locking the version. If you look at the provisioning you've got v1.1 installed but you don't have the updated unit tests from this PR to make them pass. So like I said, if you run git merge origin/master on your local branch and re-push, this unit test will pass. Or you can merge this PR and since all of the other unit tests passed, it should mean everything in master will pass too. Up to you.