Wrapping a rule with a macro of the same name prevents the rule from being documented

One pattern in use in repos is to override a rule with a macro so that additional targets can be generated without needing to rewrite existing callers. An example of this approach [can be seen in this PR](https://github.com/bazelbuild/rules_kotlin/pull/529).

`stardoc` will document the macro, but will not find the wrapped rule, and so will not correctly document the project.

Start by reproducing the wrapped-rule and same-name macro pattern described in the issue, using the linked rules_kotlin PR as the example. Then trace how stardoc discovers and documents rules versus macros; done means the wrapped rule is documented correctly alongside the macro.

Written by the indexing model from the issue text.