[INFRA] Reduce the number of GitHub job runs for e2e tests #3196
Description
First improvements were done with #2172 that already improve the situation a lot.
Detection of Dependencies change
We could reduce the number of e2e tests run when some dependencies are updated.
Currently, we run the tests each time the package.json changes. When a production dependency changes, we must run the tests.
But, there are a few development dependencies that impact the e2e tests (jest, ts-jest, playwright and probably others). Can we skip running the tests when non related dependencies change?
https://github.com/tj-actions/changed-files let get the list of changed files and detect if package.json and package-lock.json are the sole changed files in the PR.
The code of https://github.com/MontyD/package-json-updated-action could be use to retrieve the previous and current version of the files and perform the diff.
Tested browsers
Do we need to test all browsers with all OS every time?