Fix azure protobuf

[GavinFrazar]

I made a mistake in #15673 yesterday adding a field to Azure metadata protobuf, giving "ResourceID" the same json key as "Name".

[zmb3]

Change looks good, but feels like there should be a linter that can catch this and prevent it from happening again. Mind investigating?

[r0mant]

Wouldn't #15856 catch things like this? cc @codingllama

Although it looks like "legacy" protobufs are ignored there.

[zmb3]

I would think it best to have a Go linter that catches this in the generated code, as opposed to trying to teach buf about gogoproto.jsontag.

[zmb3]

In fact, looks like go vet catches this:

go vet ./...
# github.com/gravitational/teleport/api/types
types/types.pb.go:1375:2: struct field ResourceID repeats json tag "name" also at types.pb.go:1373

[codingllama]

Wouldn't #15856 catch things like this? cc @codingllama

Although it looks like "legacy" protobufs are ignored there.

I don't think linters would go as deep as gogo JSON tags, sadly.

Btw, since we are talking about this, I do have a follow up to enable some linting in legacy protos. Just wait for it. :)

[github-actions]

@GavinFrazar See the table below for backport results.

Branch	Result
branch/v10	Failed
branch/v7	Failed
branch/v8	Failed
branch/v9	Failed