Enforce proto and go sdk chain IDs are in sync via a test

[evan-gray]

Description and context

PRs like #3955 could be avoided if a test enforced that there is chain ID parity between the SDK and the generated proto go files. It is already enforced that what the proto files generate match what is committed. This seems like the next logical step.

Definition of done

Changing the chains in sdk/vaa/structs.go requires changing them in proto/publicrpc/v1/publicrpc.proto (and vice-versa), enforced via a go test or CI check.