[py][js] Initial Creation of a external shippable selenium manager

[AutomatedTester]

this adds the ability to call npx or uvx to be able to call selenium manager and it handles the scenarios around picking the correct version for your computer

🔗 Related Issues

This is creating the shippable parts of #17326

💥 What does this PR do?

🔧 Implementation Notes

🤖 AI assistance

• No substantial AI assistance used
• AI assisted (complete below)
  • Tool(s): Claude
  • What was generated:
  • I reviewed all AI output and can explain the change

💡 Additional Considerations

🔄 Types of changes

• New feature (non-breaking change which adds functionality and tests!)

[nvborisenko]

Would be amazing to ship it for dotnet too, dnx command. Some info: https://andrewlock.net/exploring-dotnet-10-preview-features-5-running-one-off-dotnet-tools-with-dnx/

[cgoldberg]

Should we add the architecture name to the Windows packages? (like they are for Linux)
i.e.: selenium-manager-windows-x86-64 instead of selenium-manager-windows

That will give us the ability to ship ARM64 Windows builds in the future and differentiate them easily.

Also, is that naming convention forced by the package repos, or can we unify them between JS and Python?

i.e. publish both packages as selenium-manager-macos, instead of selenium-manager-darwin and selenium-manager-macos?

[titusfortner]

I have a number of concerns that I'll enumerate on Slack.

The first one - if we are releasing this independently we can (and should) make the plausible tracking opt-in instead of opt-out.