Expose defs.bzl form resolved_interpreter_os_alias as a target

[UebelAndre]

PR Checklist

Please check if your PR fulfills the following requirements:

• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature (please, look at the "Scope of the project" section in the README.md file)
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

What is the current behavior?

This broke my stardoc targets when I went to plug in the new toolchains to pip_parse since I have all that in macros that are called by other repositories.

Issue Number: N/A

What is the new behavior?

This allows users to access {name}_resolved_interpreter//:defs.bzl as a target so stardoc can successfully generate documentation.

Does this PR introduce a breaking change?

• Yes
• No

Other information

[alexeagle]

Yup looks right, same reasoning as

rules_python/python/pip_install/pip_repository.bzl

Lines 118 to 119 in 1b59002

	# Ensure the `requirements.bzl` source can be accessed by stardoc, since users load() from it
	exports_files(["requirements.bzl"])