Set buildvcs flag to false in docker build.

[psigen]

What changed?

I added a -buildvcs=false flag to the go build step inside the dockerfile.

Why?

This is a workaround to #156
I'm not sure if this is the best way to do this, but it does work.

How did you test it?

I ran docker build . before and after the change.

Potential risks

This may strip VCS information that someone is using, I am not sure if it is necessary to use this flag in the docker image.

Is hotfix candidate?

No

[sagikazarmark]

I'm not entirely sure temporalite is supposed to be used as a submodule. IMO it's an edge case enough to not disable the buildvcs flag by default.

If all else fails, I'd recommend adding a build arg so that you can manually disable it during a docker build.

[wit-0-bit]

I'm not entirely sure temporalite is supposed to be used as a submodule.

Maybe I am missing something here, but why should it matter if it's in a submodule? For context, I've a docker based development setup which needs to be distributed across a small team. Adding this project as a submodule and referencing the Dockerfile here in the docker compose file seemed like it would have been a pretty reasonable thing to do but I was blocked by this issue. I ended up making another Dockerfile and grabbing a binary from the release page.

To be clear, I am not saying this flag should be disabled. Admittedly I am not sure exactly what the flag does or how it benefits a docker build.