chore(concatjs_devserver): Updated io_bazel_rules_go dependency

[KrauseStefan]

PR Checklist

Please check if your PR fulfills the following requirements:

• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature (please, look at the "Scope of the project" section in the README.md file)
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

What is the current behavior?

Using the old version

Issue Number: N/A

What is the new behavior?

Using the new version without the path

Does this PR introduce a breaking change?

• Yes
• No - Hope not

Other information

White debugging some other issue I updated this dependency thinking that might solve the problem, turns out it did not but instead of throwing the code away I will would ask if you where interested in this update

References
bazelbuild/bazel#12744
bazel-contrib/rules_go#2076

CC @alexeagle

[KrauseStefan]

Re created PR #2360 as it was closed when the 3.x branch was deleted

[github-actions]

This Pull Request has been automatically marked as stale because it has not had any activity for 90 days. It will be closed if no further activity occurs in two weeks. Collaborators can add a "cleanup" or "need: discussion" label to keep it open indefinitely. Thanks for your contributions to rules_nodejs!

[github-actions]

This PR was automatically closed because it went two weeks without a reply since it was labeled "Can Close?"