ref(templates/go): use spinframework import path

[adamreese]

There's no tagged releases for the new Go SDK. This pins the SDK in the templates to a git sha.

[adamreese]

Right after opening this, I'm thinking we may want to cut a release of the SDK in it's new home first.

[vdice]

Right after opening this, I'm thinking we may want to cut a release of the SDK in it's new home first.

I think it would be nice to pin to a known release. I wasn't sure what the release strategy in the upstream go SDK is, what with the push to support wasip2.

[itowlson]

@adamreese I rebased this in the hope of fixing the unrelated JS CI failure. If it now passes, do you want me to approve and merge, or are you still pondering pinning a known release?

[adamreese]

I didn't feel fully confident making the decision to bump the existing repo. A big reason being that there's some POC's out there that are using the wasip2 branch. The code in the branch is under the /v2 path. I'll raise the question again to see if anyone has feelings now on it. Otherwise, I'll make the call this week.

[adamreese]

Tracking issue for the SDK version: spinframework/spin-go-sdk#22

[adamreese]

@itowlson I'm going to tag the SDK but a few changes need to get in first that are pending review. I'll update this PR when the SDK is tagged

[adamreese]

Upstream SDK has been tagged. This is good to go

[itowlson]

@adamreese CI for new PRs (i.e. using the updated templates) is failing with

go: errors parsing go.mod:
go.mod:5: require github.com/spinframework/spin-go-sdk: version "v2.2.1" invalid: should be v0 or v1, not v2

[adamreese]

@itowlson Go mods strikes again. I foobared it #3198