fix(e2e): don't double run cypress tests

[pieh]

This hopefully fixes failing cypress tests running twice in CI due to lovely "cy:run": "(is-ci && cypress run --browser chrome --record) || cypress run --browser chrome" npm scripts we use (--record seems problematic when not used with CYPRESS_PROJECT_ID and CYPRESS_RECORD_KEY env vars

Targets #28169 which should be much more straight forward #28169 was merged, so targets master branch now

[pieh]

I'll just say that I don't love the extra abstraction that I add here (script that replaces cypress run and also need to parse same args and translate them to Cypress Node API), but as far as I know there is no cross platform if-else command that could do something like is-ci ? run-cypress-with-record : run-cypress-without-record

[pieh]

Ok, from some chatting - I will drop calling cypress.run from node and instead go with

node scripts/some-good-name-for-the-script.js "cypress run [...] --record" "cypress run [...]" that would check if we are in CI and for existence of needed env vars and run one of those commands based on that (with exaca or so)