Summary

This is a documentation-only follow-up to GH-152906.

After the Windows wildcard normalization fix was merged, follow-up discussion highlighted that os.DirEntry.path intentionally preserves the original os.scandir() argument rather than a normalized path.

This PR clarifies the documented semantics of DirEntry.path, including:

• DirEntry.path is constructed from the original os.scandir() argument and entry.name.
• Relative scandir() arguments produce relative DirEntry.path values.
• Changing the current working directory after creating the iterator can affect how relative DirEntry.path values resolve.
• On some platforms, a path accepted for enumeration may not necessarily produce a valid path when later joined with the filename.

This PR is documentation only and does not change runtime behavior.

• Issue: On Windows scandir handles paths different from other filesystem APIs #150880