[Bug]: build-publish-container-goreleaser ignores the `go_version_file` input

[seantronsen]

Describe the bug

The || 'stable' fallback means go-version is never empty, so a caller passing only
go_version_file gets both inputs. setup-go warns Both go-version and go-version-file inputs are specified, only go-version will be used and installs stable, silently
discarding go.mod.

Steps to reproduce

Run the workflow.

Code of Conduct

• I agree to follow this project's Code of Conduct

[seantronsen]

https://github.com/actions/setup-go

mentions go_version takes precedence.