Allow path-only datasets in manifest schema

[cortadocodes]

Summary

Allow a manifest's datasets to be specified as paths, allowing metadata to be gathered dynamically from these datasets instead of hard-coded in a manifest serialisation.

Contents (#101)

IMPORTANT: There are 2 breaking changes.

Enhancements

• BREAKING CHANGE: Make Twine.available_strands a set instead of a tuple
• Update manifest schema to allow path-only datasets
• Raise error if a dataset specified in a manifest strand of the twine is missing from the corresponding manifest
• Add Twine.available_manifest_strands property

Refactoring

• BREAKING CHANGE: Move dataset files tag checking into octue-sdk-python at octue.runner.Runner._validate_dataset_file_tags

Refactoring

• Move manifest and twine migrations into migrations subpackage

[codecov[bot]]

Codecov Report

Merging #101 (d6df9e3) into main (1e4dbcf) will increase coverage by 0.68%. The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #101      +/-   ##
==========================================
+ Coverage   87.64%   88.32%   +0.68%     
==========================================
  Files           7        9       +2     
  Lines         267      274       +7     
==========================================
+ Hits          234      242       +8     
+ Misses         33       32       -1     

Impacted Files	Coverage Δ
twined/migrations/manifest.py	100.00% <100.00%> (ø)
twined/migrations/twine.py	100.00% <100.00%> (ø)
twined/twine.py	81.81% <100.00%> (+0.05%)	:arrow_up:

---

Continue to review full report at Codecov.

Legend - Click here to learn more Δ = absolute <relative> (impact), ø = not affected, ? = missing data Powered by Codecov. Last update 1e4dbcf...d6df9e3. Read the comment docs.