Freature: hard-set adjustment year

[irm-codebase]

Fixes #13

Summary of changes in this pull request

• Adjustment year is non-configurable, and instead it is set to latest year that EIA / input datasets allow.
• CRS in configuration file follows the same standard as other modules

Reviewer checklist

• There are no pip dependencies in the module's environment files (workflow/envs/).
• All rules use pathvars (e.g., <results>) in their inputs and outputs.
• The integration test-suite is successful, including:
  • pre-commit.ci tests pass.
  • tests pass for all relevant OS configurations (linux, osx, windows).
• Module documentation is up-to-date, including:
  • INTERFACE.yaml mentions all relevant pathvars and wildcards.
  • README.md describes how to use the module and has the necessary citations.