Feature/flux model v1 4 0 run

[dagibbs22]

Pull request checklist

Please check if your PR fulfills the following requirements:

• [] Make sure you are requesting to pull a topic/feature/bugfix branch (right side). Don't request your master!
• [] Make sure you are making a pull request against the develop branch (left side). Also you should start your branch off our develop.
• Check the commit's or even all commits' message styles matches our requested structure.
• 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
• 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?

1. carbonflux package used forest flux model v1.3.2.
2. carbonflux package output emissions for CO2, non-CO2, and all gases combined.
3. carbonflux package used 10-km drivers map

What is the new behavior?

1. carbonflux package uses forest flux model v1.4.0
2. carbonflux package outputs emissions for CO2, CH4, N2O, non-CO2 gases combined, and all gases combined.
3. carbonflux package uses 1-km driver map

Does this introduce a breaking change?

• Yes
• No

Other information

Uses GDAL 3.1.2. Was not able to run this locally and had to test GMB and IDN14.13 in EMR through the sbt shell.

[danscales]

Generally, it looks good.

But, did you notice that the tests failed? That's because we now have two tests for annualupdate_minimal. Does it make sense that the results for annualupdate_minimal changed? I see that it use netFluxCo2 and grossEmissionsCo2e{NonCo2,CO2Only}, etc. in its analysis, so it probably does, since you updated versions of some of those datasets, but you should probably double-check. If it seems fine, then I can show you how to update the test results so the annualupdate_minimal tests pass again.

[danscales]

Looks good. I'll fix the tests.