How to create go_proto_library automatically

### What version of rules_go are you using?
`v0.47.0`

### What version of gazelle are you using?

`v0.35.0`

### What version of Bazel are you using?
`6.3.2`

### Does this issue reproduce with the latest releases of all the above?

I don't know.

### What operating system and processor architecture are you using?

```
Linux 30eedc3eab42 5.15.146.1-microsoft-standard-WSL2 #1 SMP Thu Jan 11 04:09:03 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
```

### Any other potentially useful information about your toolchain?

### What did you do?

I use 'bazel run //:gazelle' to generate BUILD.bazel.

### What did you expect to see?

Create `go_proto_library`.

### What did you see instead?
I only found `proto_library`. I looked up some information and couldn't locate a solution.

Start by reproducing the reported `bazel run //:gazelle` command with rules_go v0.47.0, Gazelle v0.35.0, and Bazel 6.3.2, then inspect the generated BUILD.bazel output. Determine how proto inputs are discovered and whether the requested `go_proto_library` generation is supported or needs documentation or implementation. Done means the expected generation behavior is clearly established and reproducible.

Written by the indexing model from the issue text.