Remove Chrome Logger and update Cypress and Percy

[gabrieldutra]

What type of PR is this? (check all applicable)

• Other

Description

This removes the Chrome Logger (was causing issues with Cypress requests).

Also took the opportunity to:

• Revert Update npm run to fix hpe_header_overflow in recent nodejs versions #3732 (no longer necessary without the chrome logger)
• Revert Cypress: Force readonly inputs click #4016 (no longer necessary with Cypress@3.5.0)
• Use the "server" command instead of "dev_server" for Redash in Cypress CI

Other than the chrome logger, solved some other issues that appeared in the specs.

Related Tickets & Documents

Closes #4286.

Mobile & Desktop Screenshots/Recordings (if there are UI changes)

--

[gabrieldutra]

The Tooltip was still up in front of some parameter inputs after clicking in "Apply All", blocking tests to continue

[gabrieldutra]

Percy highlighted that the Tooltip issue was not isolated to the Apply All button, now all clicked objects show their tooltips and since there's no unhover action on the tooltip or in the wrapped object, it stays open.

[gabrieldutra]

@kravets-levko I wonder how this snapshot could change just by updating Cypress/Percy 🤔. You think it's a valid result too? (for me it's good, just need to be stable like that)

[kravets-levko]

@gabrieldutra I may be caused by different visualization container width (but not sure what may cause this, though). Both results look valid (there are no partially visible elements, font looks the same and so on), but the most reliable way to check which snapshot is correct is to run this test locally with the same browser window size we use for Percy. Also, I'm not sure if it will be stable result.

[gabrieldutra]

Thanks @kravets-levko I actually just wanted to make sure it was still valid 😅, the rest I don't think it's worth it to be testing manually, we will see what happens over time :)