I think in the interest of having package names matching the import
paths, the module definition in go.mod should be considered
So github.com/jackc/pgproto3/v2 module should create
Source package golang-github-jackc-pgproto3 (the source repo may remain
same across version bumps - I'm not sure about it, as a new binary
package will have to go through a NEW visit anyway, but keeping salsa
repo names may be better)
Binary package golang-github-jackc-pgproto3-v2-dev
If this is not the expected way of doing, we should probably document
the best practice somewhere.