fix: revert f235aae (part 2)

[julienrbrt]

Description

When testing the server changes (ref #16698), I have noticed that grpcui and grpcurl were broken because of that update.
follow-up of #16534.
I think we should strive for compatibility and still revert f235aae as well for the SDK.

cc @tac0turtle as you were involved in the discussion in #16534

---

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

• included the correct type prefix in the PR title
• added ! to the type prefix if API or client breaking change
• targeted the correct branch (see PR Targeting)
• provided a link to the relevant issue or specification
• followed the guidelines for building modules
• included the necessary unit and integration tests
• added a changelog entry to CHANGELOG.md
• included comments for documenting Go code
• updated the relevant documentation or specification
• reviewed "Files changed" and left comments if necessary
• confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

• confirmed the correct type prefix in the PR title
• confirmed ! in the type prefix if API or client breaking change
• confirmed all author checklist items have been addressed
• reviewed state machine logic
• reviewed API design and naming
• reviewed documentation is accurate
• reviewed tests and test coverage
• manually tested (if applicable)

[tac0turtle]

what is the error causing the issue?

[julienrbrt]

what is the error causing the issue?

grpcurl still supports reflection v1beta1 only and grpcui as well (https://github.com/search?q=repo%3Afullstorydev%2Fgrpcui%20NewClient&type=code)

[alexanderbez]

utACK

[tac0turtle]

makes sense, need to add nolint or add the rule to golangci.yaml