feat: env to use path params in download url

[HarlesPilter]

• Closes Installing Cypress with CYPRESS_DOWNLOAD_MIRROR and Artifactory #15697

User facing changelog

Add CYPRESS_DOWNLOAD_PATH_PARAMS env variable to use path based params instead of query based params in download url.

Additional details

• Why was this change necessary? - After Add Paths and .zip to Download URLs #17291 was merged there was no way to switch the download url form query based parameters to path parameters.
• What is affected by this change? -> Cypress CLI. Support for new env variable

How has the user experience changed?

If the CYPRESS_DOWNLOAD_PATH_PARAMS is set to true then cypress is downloaded using path based params(https://download.cypress.io/desktop/0.20.2/OS-ARCH/cypress.zip)
If the new env variable is not used then download url doesn't change (uses query based params https://download.cypress.io/desktop/0.20.2?platform=OS&arch=ARCH)

PR Tasks

• Have tests been added/updated?
• [na] Has the original issue (or this PR, if no issue exists) been tagged with a release in ZenHub? (user-facing changes only)
• Has a PR for user-facing changes been opened in cypress-documentation? docs: added documentation for CYPRESS_DOWNLOAD_PATH_PARAMS cypress-documentation#4299
• [na] Have API changes been updated in the type definitions?
• [na] Have new configuration options been added to the cypress.schema.json?

[cypress-bot]

Thanks for taking the time to open a PR!

• Create a Draft Pull Request if your PR is not ready for review. Mark the PR as Ready for Review when you're ready for a Cypress team member to review the PR.
• Become familiar with the Code Review Checklist for guidelines on coding standards and what needs to be done before a PR can be merged.

[mjhenkes]

Hi @HarlesPilter, thank you for taking the time to contribute! This is a good start and definitely will help us cover a gap where the users download proxy isn't 1:1 with our download server. I would ask you to expand the scope of the change a bit though.

With this PR we're covering the case where the version of cypress the user wants to download is located at exactly ${endpoint}/${platform}-${arch()}/cypress.zip but I can't be sure that is covering all use cases as urls could vary wildly between different setups.

I'd like to propose that instead of taking a boolean we take a string template. That way a user can exactly specify how they want their download url constructed.

For example:
We change your ENV from CYPRESS_DOWNLOAD_PATH_PARAMS to CYPRESS_DOWNLOAD_PATH_TEMPLATE

And You'd set CYPRESS_DOWNLOAD_PATH_TEMPLATE='${endpoint}/${platform}-${arch()}/cypress.zip'

The logic would update to check if the CYPRESS_DOWNLOAD_PATH_TEMPLATE is valued, then sub in endpoint, platform and arch, then use the download url. This would allow for all kinds of different download paths

• '${endpoint}/${platform}-${arch()}/cypress.zip' Your version
• '${endpoint}/${platform}/${arch()}/cypress.zip' slash separating architecture
• '${endpoint}/cypress.zip' completely ignoring platform and architecture for some reason.

[HarlesPilter]

Good idea! Implemented the CYPRESS_DOWNLOAD_PATH_TEMPLATE, but I used ${arch} in the template instead of ${arch()}