Update imports for v2 compatibility

[saley89]

For #77

This resolve the go install issue and honours go package structure correctly now. Essentially when the git versioning moved to v2.X.X we should have introduced /v2 into the module name. There are various ways to package it up when this happens including having all of the V1 code at root and then having a copy go into a v2 subfolder and development continue in there, with the v1 root being for backwards compatibility.

However, I believe we only want one version of the code in our master. As such, this PR moves the module entirely to v2. Thus, go install now works as expected using this:

go install github.com/sky-uk/osprey/[email protected]

Indeed you can even use @latest and it will find the current v2.8.0 version:

go install github.com/sky-uk/osprey/v2@latest

The previous command will always find v1.5.0 as that is the "latest" version of v1:

go install github.com/sky-uk/osprey@latest

Please let me know your thoughts on the above and if we are happy to merge this in.

Possible useful docs -> https://go.dev/blog/v2-go-modules

[aecay]

seems correct to me -- aiui this is the (or a) correct way to release v2 of a go program. dunno if you want to wait for more reviews/consensus before merging in but i'm personally happy with it.

[howardburgess]

Looks good to me. I agree, no need to keep v1 hanging around too.