get-tool-intel-pin: add path.# variation for custom installation path

[YasirKhokhar]

What
Adds a path.# variation to get-tool-intel-pin to support specifying a custom PIN tool installation directory via --pintool_dir= CLI flag.

Why
Without this variation, the cache key for get-tool-intel-pin does not include the installation path, so passing a custom path would always hit the cached entry from the default installation effectively ignoring the custom path.

The path.# variation ensures that each unique path gets its own cache entry, making custom PIN tool installations work correctly and cache-safely.

[github-actions]

MLCommons CLA bot:
Thank you very much for your submission; we really appreciate it. Before we can accept your contribution,
we ask that you sign the MLCommons CLA (Apache 2). Please submit your GitHub ID to our onboarding form to initiate
authorization. If you are from a MLCommons member organization, we will request that you be added to the CLA.
If you are not from a member organization, we will email you a CLA to sign. For any questions, please contact
support@mlcommons.org.
0 out of 1 committers have signed the MLCommons CLA.
❌ @YasirKhokhar
_{You can retrigger this bot by commenting recheck in this Pull Request}

[arjunsuresh]

Looks good @YasirKhokhar Can you please change the commit user to the GitHub user with AMD email? Merge to Mlcommons requires CLA signing.

[YasirKhokhar]

recheck

[arjunsuresh]

@YasirKhokhar can you please change the commit author email to your AMD email address?