Fix config scopes

[gabegma]

Description:

• I fixed a few issues with config scopes and expirable modules. Modules don't need AzimuthConfig as a scope if they are affected by smart tags, as long as they are ExpirableModules. Since FilterableModules are already ExpirableModules, they were all ok except MetricsbyFilter.
• I also separated the metrics from the ModelContractConfig, to avoid recomputing all predictions if we only change the metrics.

Checklist:

You should check all boxes before the PR is ready. If a box does not apply, check it to acknowledge it.

• ISSUE NUMBER. You linked the issue number (Ex: Resolve #XXX).
• PRE-COMMIT. You ran pre-commit on all commits, or else, you
  ran pre-commit run --all-files at the end.
• USER CHANGES. The changes are added to CHANGELOG.md and the documentation, if they impact
  our users.
• DEV CHANGES.
  • Update the documentation if this PR changes how to develop/launch on the app.
  • Update the README files and our wiki for any big design decisions, if relevant.
  • Add unit tests, docstrings, typing and comments for complex sections.

[gabegma]

When you have a chance, could you take a look and make sure that this makes sense to you @Dref360, our caching expert?

[Dref360]

LGTM

[JosephMarinier]

I have one naming comment, and that's it! Good job! 👍