additional debug in _findMatch for osVersion & platform_version needed to make sense of earlier debug statements

Describe the bug
additional debug in _findMatch for osVersion & platform_version is needed to make sense of earlier debug statements

Currently no debug displays the osVersion identified and the expected platform_version. This leads to the debug for architecture display valid comparisons like #[debug]x86===x86 && linux===linux but no subsequent reason for the osVersion check to work. The present state is confusing

To Reproduce
Run actions/setup-python on a platform that isn't support by the action (e.g. RHEL).

Expected behavior
debug needs to display versions for clarity.

Screenshots

  ##[debug]check 3.10.14 satisfies 3.10
  ##[debug]x64===x64 && darwin===linux
  ##[debug]x64===x64 && linux===linux
  ##[debug]arm64===x64 && linux===linux
  ##[debug]x64===x64 && linux===linux
  ##[debug]arm64===x64 && linux===linux
  ##[debug]x64===x64 && linux===linux
  ##[debug]check 3.10.13 satisfies 3.10

Despite successful matches, no info as to why those failed.

Desktop (please complete the following information):
All platforms.

Additional context
Add any other context about the problem here.

Search the TypeScript sources for _findMatch and inspect the existing architecture and platform debug statements. Reproduce the lookup on an unsupported platform such as RHEL; done means the debug output identifies the detected osVersion and expected platform_version so failed matches are explainable.