Do not use the default namespace for the `maven.install` tag

Using the default `maven` namespace causes pollution for projects that depend on `rules_closure`. I'm attempting to use `rules_closure` with Selenium itself, and introducing the ruleset has lead to the unusual condition that we now depend on our own published jars.

In `rules_jvm_external` we advise against rulesets included via `bazel_dep` from using the default namespace ([in this section](https://github.com/bazel-contrib/rules_jvm_external/blob/master/docs/bzlmod.md#module-dependency-layering)) Perhaps `closure_deps` could be used instead?