Closed issue by vixus0 on void-packages repository

https://github.com/void-linux/void-packages/issues/27690

Description:
### Problem

When using the `build_style=go`, package templates may be using a `go_import_path=` that does not match the name of the go package. This could be because the package name changed in the upstream source. The result is a seemingly correct package that was actually built from very old sources thanks to the way go works. I suspect this is mainly likely to happen with go sources that make use of go modules but as that becomes more standard it might become more likely.

For an example, see #27688.

### Mitigations

- Linting: when `go.mod` is present, check that `go_import_path=` is set to the name defined there.
- `build-style/go.sh`: (better, imo) set the value of `go_import_path=` to the module name defined in `go.mod`.