Integrate Dynamic Settings

[davidshq]

Dynamic Settings

• Add two new models: setting and settings_group (these hold and group the dynamic settings).
• Use the built-in Python logging library in Project model and tasks.py.
• Fields added to the Project model that map to the Settings model.
• Remove default_identified_artifacts and pass an empty array at the global level instead.
  • This is per conversation in PR 574 in OpenImaging MIQA repo: https://github.com/OpenImaging/miqa/pull/574 where it was requested that transforming of artifacts be handled on the client (Vue) side and be set per-project.
• Modify tasks.py so that it can use the dynamic settings for determining the learning models to load.
• Add a setting.json file which contains a base configuration for MIQA that can be imported when setting up a new instance.

Misc

• Add an AUTO_ADVANCE flag which determines whether scans advanced automatically after a decision is rendered.
• Update GitHub Actions yaml files to use most recent versions of actions available atm.
• Disabling Playwright temporarily from CI due to need to setup backend for frontend testing.
• Update .gitattributes to fix some issues with some binary files being detected as changed even when they aren't.
• Exclude test files from extraneous dependencies ESLint rule.

[davidshq]

@annehaley - this one should be ready to go except that for some reason the CI is having trouble finding itk. not sure if you have any ideas? I reverted the github actions I'd updated but that doesn't seem to have resolved the issue