feat: Remove hardcoded rule kinds requirement for source-code generators

[ghorak-happening]

Checklist

• I have filed an issue about this change and discussed potential changes with the maintainers.
• I have received the approval from the maintainers to make this change.
• This is not a stylistic, refactoring, or cleanup change.

Please note that the maintainers will not be reviewing this change until all checkboxes are ticked. See
the Contributions section in the README for more
details.

Discussion thread for this change

Issue number: #6428

Description of this change

Removing hardcoded proto rule name to enable other Go code generators

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[sgowroji]

Hi @ghorak-happening, CLA is not signed for below mentioned email id. Can you do it to move the CLA passed for this PR.

❌ 295b770 Author: @ghorak-happening <gor******ak​@happening.xyz>

[sgowroji]

Hi @ghorak-happening, Can you please go through the complete steps mentioned here https://github.com/bazelbuild/intellij/pull/6429/checks?check_run_id=30712727372

[agluszak]

@ghorak-happening why is this a draft?

[ghorak-happening]

Hi,

@sgowroji, I went through the proces several times. I am required to sign corporate CLA, not personal CLA (my colleague Mislav is discussing this over Slack with you)

@agluszak I've left the PR in draft until the CLA issue is solved, if you'd like, I can remove it from draft.

[ghorak-happening]

Hi,

I've successfully completed the CLA process and published this PR out of draft. Please advise on the next steps.

cc @sgowroji @agluszak