IP-242 - Add .snyk file.

[owenlittlejohns]

Description

This PR builds on some work that @flamingbear has done in other repositories to add a .snyk file that will ensure Snyk uses the correct version of Python when building an environment to scan the Harmony Regridding Service dependency tree. This will avoid false positives in our Snyk scans.

This change does not impact the service and only relates to our CI/CD (so it doesn't need a release or updated notes in the change log).

(Side note - we should separately bump the version of Python used from 3.9 to something more like 3.11, but that can be separate to this PR)

Jira Issue ID

N/A

Local Test Steps

• Check the version of Python listed in docker/service.Dockerfile matches the one in .snyk.
• After merging, check the version of Python Snyk uses is correct.

PR Acceptance Checklist

• Jira ticket acceptance criteria met.
• CHANGELOG.md updated to include high level summary of PR changes.
• docker/service_version.txt updated if publishing a release.
• Tests added/updated and passing.
• Documentation updated (if needed).

[owenlittlejohns]

Old, but matching the service for now. I'll add bumping the Python version for the service to my to-do list.

[flamingbear]

was coming to ask why not bump the service version too. but this is fine

[owenlittlejohns]

I'll try and take a look at bumping the service in the next day or so. Now that I'm reading this thread back, I'm feeling like I was being lazy.

[owenlittlejohns]

Alrighty, @flamingbear - it's all bumped to Python 3.11. Probably needs some more testing, likely running the regression test notebook against Harmony in a Box.

[flamingbear]

It'll be nice to bump the service version too, but this works.

[flamingbear]

So I would say this is good, but I would also change the python version in this comment and in this one.

Otherwise it all looks good to me.

[owenlittlejohns]

@flamingbear - nice catch on the documentation notebook. I've tweaked that now. I bumped the dependencies. It looks like it all runs nicely now, but I had to specify another dependency version (which was otherwise installed) to squash a bunch of deprecation warnings.