Feature/flux model v1 2 2 run

[dagibbs22]

Pull request checklist

Please check if your PR fulfills the following requirements:

• [x] Make sure you are requesting to pull a topic/feature/bugfix branch (right side). Don't request your master!
• [x] Make sure you are making a pull request against the develop branch (left side). Also you should start your branch off our develop.
• [x] Check the commit's or even all commits' message styles matches our requested structure.
• [x] Check your code additions will fail neither code linting checks nor unit test.

Pull request type

Please check the type of change your PR introduces:

• [ ] Bugfix
• [x] Feature
• [ ] Code style update (formatting, renaming)
• [ ] Refactoring (no functional changes, no api changes)
• [ ] Build related changes
• [ ] Documentation content changes
• [ ] Other (please describe):

What is the current behavior?

Previous version used flux model v.1.2.1 (2001-2020 tree cover loss) outputs.

What is the new behavior?

• Uses flux model v1.2.2 (2001-2021 tree cover loss) outputs.
• Emissions now includes columns for emissions from soil only (not just biomass and soil).
• Change tables include removals by year of tree cover loss.
• Made output fields match the API (annualupdate_minimal package) output fields.
• Used other changes to Geotrellis that Justin had implemented, plus a few little fixes to make it launch correctly from the sbt shell in IntelliJ.
• Reverted to using 200 worker instances (100 in previous year, I believe).

Does this introduce a breaking change?

• [ ] Yes
• [x] No

Other information

N/A