Description:

I'm trying to run the Go SDK v0.8.8 and v0.9.1 and I'm getting the following error with the current v0.9.1 version of the `dagger` package:

```
$ dagger run go run main.go
┣─╮
│ ▽ init
│ █ [1.22s] connect
│ ┣ [1.18s] starting engine
│ ┣ [0.04s] starting session
│ ┃ OK!
│ ┻
█ [1.45s] go run main.go
┃ Building with Dagger
┃ failed to check version compatibility: input:1: checkVersionCompatibility failed to parse engine version as semver: No Major.
┃ Minor.Patch elements found
█ [0.00s] ERROR checkVersionCompatibility(version: "0.9.1")
┻
• Engine: 29313be02785 (version main)
⧗ 2.68s ✔ 4 ✘ 1
$ dagger version
dagger devel (ed98d775a) (registry.dagger.io/engine) linux/amd64
```

I think that the `dagger` service needs a SemVer on build to be able to talk to connecting clients, and the compiled version of `dagger` in this package has a fallback `devel` hash injected during build. Apparently connecting clients don't like to be served that `devel` fallback version string.


Additional info:
* package version(s): v0.8.8 and v0.9.1 (current)

Steps to reproduce:
- create a "hello world" Go Dagger SDK program
- run `dagger run go run main.go`
- the build process returns a version string error (assumably when the Go SDK tries to connect to the Dagger service)

The solution would be to make sure the actual SemVer version string is injected during the build process; or perhaps ping the Dagger developers about being more flexible in the client SDK.