Exclude dist-info data from pip_repository targets

[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?

Issue Number: N/A
This is a continuation of

• Ignore __pycache__ contents and *.pyc files in external dependencies #570 (comment)
• feat: cpython toolchains #618 (comment)

What is the new behavior?

The dist-info directory of a wheel is excluded from the py_library targets as they may contain volatile data.

Does this PR introduce a breaking change?

• Yes
• No

Other information

[UebelAndre]

cc @mattem who I think would be a good reviewer.

[mattem]

I'm not sure what else in dist-info might be needed, or if anything is. However, we'll want ** as the prefix as some packages contain nested dist-info dirs, internally we patch in "**/*dist-info/RECORD". I'll try and dig out the package we hit this one (that could take me a while, don't block)

Suggested change

	"*dist-info/**",
	"**/*dist-info/**",

[UebelAndre]

I've applied this patch but think it would be good to know the packages. I'm also not necessarily advocating for excluding all of dist-info, I just don't know of a case where it's needed and I know it contains non-deterministic data. Happy to go with something more focused for now. I leave it up to you.

[mattem]

I'll dig them out next week. I think this is likely fine to merge as is. Can always revert or update if it causes issues.

[UebelAndre]

@mattem I've opened a followup at #632 after doing wider testing of these changes.