fix: Use js_binary in macro in external repository

[mvgijssel]

---

Type of change

• Bug fix (change which fixes an issue)

Test plan

• Manual testing; please provide instructions so we can reproduce:

In vgijssel/setup#601 I tried using js_binary from within a macro called release_manager which was located in the rules_release workspace. The rules_release macro was called from the main workspace which resulted in the following error:

ERROR: Analysis of target '//:release_manager' failed; build aborted: no such package '@[unknown repo 'aspect_rules_js' requested from @]//js': The repository '@[unknown repo 'aspect_rules_js' requested from @]' could not be resolved: No repository visible as '@aspect_rules_js' from main repository
INFO: Elapsed time: 0.188s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (0 packages loaded, 0 targets configured)
ERROR: Build failed. Not running target

After asking in the Bazel community https://bazelbuild.slack.com/archives/C014RARENH0/p1698918118051159 @fmeum found the issue: the js_binary is a macro which uses labels which are not wrapped in the Label class, causing them to be scoped to the main repository. Wrapping these labels with Label class fixes the issue.

[CLAassistant]

All committers have signed the CLA.