Update runfiles lib

[fmeum]

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?

rules_python's runfiles library is affected by bazelbuild/bazel#14336, which has been fixed upstream.

What is the new behavior?

rules_python's version of the runfiles library contains bazelbuild/bazel@486d153

Does this PR introduce a breaking change?

• Yes
• No

Other information

Also adds the tests contained in the Bazel repo.

[fmeum]

@alexeagle This is the first commit with changes backported (?) from Bazel. I will start adding the Bzlmod changes as follow-ups.

[fmeum]

Is there a canonical way to format Python files? The runfiles library differs from the Bazel Core one in this regard and I would like to stay consistent with the formatting style used in this repo.

[alexeagle]

You can install pre-commit.com and run 'pre-commit install' for our typical flow. It just uses black and there's no CI enforcement IIRC

[alexeagle]

Thanks! I assume this was already reviewed when it was changed upstream so we are just updating our vendored copy

[fmeum]

I ran the formatters.

[alexeagle]

Thanks!