bzl gazelle support overwrite resolve

[eeelin]

Support using gazelle:resolve directives to overwrite dependencies resolve. Especially for some non-standard bzl naming, such as:

# gazelle:resolve starlark starlark @io_bazel_rules_docker//docker/util:run.bzl @io_bazel_rules_docker//docker/util
# gazelle:resolve starlark starlark @io_bazel_rules_docker//repositories:deps.bzl @io_bazel_rules_docker//repositories
# gazelle:resolve starlark starlark @io_bazel_rules_docker//repositories:repositories.bzl @io_bazel_rules_docker//repositories
# gazelle:resolve starlark starlark @rules_python//python:defs.bzl @rules_python//python:defs_bzl
# gazelle:resolve starlark starlark @npm//:vite/package_json.bzl @npm//:vite_bzl_library
# gazelle:resolve starlark starlark @npm//:docsify-cli/package_json.bzl @npm//:docsify-cli_bzl_library
# gazelle:resolve starlark starlark @npm//:typedoc/package_json.bzl @npm//:typedoc_bzl_library
# gazelle:resolve starlark starlark @npm//:api-spec-converter/package_json.bzl @npm//:api-spec-converter_bzl_library
# gazelle:resolve starlark starlark @rules_nodejs//nodejs:repositories.bzl @rules_nodejs//nodejs:bzl

[google-cla[bot]]

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.

[fmeum]

@brandjon This would be pretty useful to have and looks simple enough, would you be available for a review?