Promote releases to v1

[StephenHulme]

Describe the Housekeeping
This repository is currently used in production, and according to SemVer should be promoted to v1.0.0.

Blocking issues
Is there any work or decisions that need to be made before this can be released as v1.0.0?

I would suggest that Sequencescape specific releases be in the v1 series and Traction (general) releases be in the v2 series.

Additional context
There are also version number conflicts with existing repository tags in the v0 series, hampering the creation of tags and GitHub releases. I have been using release tag versions x.y.z.sanger to handle these cases.

The Traction (master) and Sequencescape (develop) branches of this repo also add a level of complexity...

[StephenHulme]

This is likely a very small task and should hopefully result in the release of at least the v1 series.

Sequencescape and/or Traction would likely require updates too.

More details of the release process can be found in #21

[BenTopping]

Is it worth trying to merge the Sequencescape and Traction functionality into a single version before this?
Might be worth a timeboxed attempt + ai might make it possible.

[StephenHulme]

That would be amazing - ideally the Sequencescape-specific functionality (I think it's just relationship polymorphism?) should live in Sequencescape as a monkey-patch, if that's possible?