Add unique provider for sh_* rules

[UebelAndre]

Description of the feature request:

I would like to write aspects that target shell rules but there’s no unique provider to key in on. Would it be possible to have a provider made to make this possible?

What underlying problem are you trying to solve with this feature?

I want to write an aspect that does linting on sh_binary targets but if --incompatible_top_level_aspects_require_providers is enabled the aspect fails since sh_binary, sh_library, and sh_test don’t return uniquely identifying providers

Which operating system are you running Bazel on?

Linux

What is the output of bazel info release?

6.1.0

If bazel info release returns development version or (@non-git), tell us how you built Bazel.

No response

What's the output of git remote get-url origin; git rev-parse master; git rev-parse HEAD ?

No response

Have you found anything relevant by searching the web?

No response

Any other information, logs, or outputs that you want to share?

No response

[comius]

Interesting. Empty providers called ShInfo would work. Probably incurring a small regression, but I think this is negligible, since I don't think large sh graphs are popular. But I might be wrong, since they are supposedly worth propagating an aspect over them

Is there any information that could be provided?

[stagnation]

One clear example of an aspect to run is shellcheck which catches a lot of the common bugs in shell-scripts. I'd rather run that with Bazel and a specific aspect than with find, and while a global aspect can work with an early exit if the kind is not sh_* is is clearly suboptimal.