Updating database migration scripts
 - create access_code should be in v0_7 b/c it wasn't in current staging database
 - add device_id must be in v0_7 b/c it's an alteration of original design
Packages symlink should be ignored
Look for dashes instead of underscores
save filename for package directory file

 - it will be {packagename}.xml
Add selectByOneskyId lookup

 - remove unneeded variable too
helper method to show initial translation status

 - used by brand new translations
Create initial OneskyResource

 - created endpoint
 - now send translatedText, not baseText in uploads
 - send locale to OneSky
Upload of multiple languages for the same package

 - multiple languages can be uploaded to oneskyapp.com
set variant to ensure things are encoded properly on our side
temporary endpoint change

upload to self so i can inspect the post content to figure out encoding
fix translation upload

- set the encoding to utf-8 on the json part
- change all parts to appropriate type
- change endpoint back to correct endpoint
- Use `ResteasyClientBuilder` instead of `ClientBuilder`
  - I honestly have no idea the difference b/w the two
downgrade httpclient

 - resteasy-client uses v4.2.1, so we should too
 - their pom stupidly doesn’t pull in the dependency so we have to
declare it here
cleanup imports
remove self-endpoint
cleanup imports
Adding this for AWS checking
Methods for creating a new translation are in place
Shored up unittests
 - includes splitting migration into two parts.  part 1 must be run first, then part 2
  - 1) database structure and non-package seed data
  - 2) content migration from file system
Code to do translation downloads from onesky for all draft GETs
refactor logic for creating a new translation
 - to its own class `NewTranslationProcess`