feat: allow computing derived resources via evaluate function

[mstechly]

Description

Adds possibility to add derived resources during routine evaluation (as opposed to only during compilation, as we do now). This change is being made to facilitate unified resources tracking elsewhere in our software stack. To this end, all machinery related to derived resources has been moved from _compile module to _common module in the same subpackage.

Additionally, this also includes following boy-scout changes:

• Adds empty lines at the top of so me modules (added by original author @mstechly )
• Updates format in pre-commit config (we were using deprecated hook names)
• Gets rid of some scipy (we were passing deprecated options to optimizers)
• Fixes typo (for whatever reason we called a single derived resource definition DerivedResources instead of DerivedResource).

Please verify that you have completed the following steps

• I have self-reviewed my code.
• I have included test cases validating introduced feature/fix.
• I have updated documentation.