feat: improved logging, scaling and documentation

[PeterBaker0]

Improves the capacity manager implementation with

• revised config parsing approach to not dynamically build zod model, but instead pull out env variables directly, and handle parsing into number where needed directly from the string environment, while still getting type hinting in the construction of the object for parsing by manipulating assumed type of the environment
• logging using winston in all methods, much more thorough logging for debugging as needed
• documentation/doc string improvements
• implemented logarithmic based scaling algorithm with controls for sensitivity + scaling factor, allowing a range of scaling behaviours, found parameters which suit our needs but can be configured
• improved management of scaling by tracking pending tasks as they start up, keeping this in sync as we poll - pending tasks are counted as towards the target task count based on the scaling function

Other changes

Also updates job interfaces to add wave height/period and make inputs optional - see open-AIMS/ReefGuideAPI.jl#67

Could do later

• expose new scaling config in the JSON config
• tidy up a few parts of the manager i.e. still not super super happy with the env parsing approach - it'd probably be nicer to make the env strictly string and then transform types using zod using the .transform method
• tooling around the scaling function to help determine suitable values against target thresholds, or to at least graph it

[github-actions]

❌ Code formatting check failed. Please run npm run format:write locally and commit the changes.

[PeterBaker0]

https://www.desmos.com/calculator/h2hxuqi2gk

Can be used to play with scaling function params

[arlowhite]

looks good. Ideally we'd have test coverage of this code, but it's tricky. At some point, I'd like to discuss if we want to create tests for this and how to approach it

[arlowhite]

ideally would have tests for these functions, but they're not so easy to test, would need to mock things. maybe an integration test? we can discuss testing approaches later

[PeterBaker0]

Yeah - there are possible options - but agree it's a bit tricky

[github-actions]

❌ Code formatting check failed. Please run npm run format:write locally and commit the changes.