The GoRPC client generator was creating variable name conflicts when service method
parameters had the same name as internally generated variables. The generator uses
fixed variable names like 'req' for request structs, but if a method parameter was
also named 'req', it would create a naming conflict in the generated code.
Another change fixes the problem with a function definition having context.Context as one of its arguments, the generated code would have the context argument twice then.

…-naming-conflicts

Bumps [actions/setup-node](https://github.com/actions/setup-node) from 5 to 6.
- [Release notes](https://github.com/actions/setup-node/releases)
- [Commits](actions/setup-node@v5...v6)

---
updated-dependencies:
- dependency-name: actions/setup-node
  dependency-version: '6'
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>

…etup-node-6

chore(deps): bump actions/setup-node from 5 to 6

…gotsrpc into fix/go-generator-naming-conflicts

fix: resolve variable name conflicts in GoRPC client generation