Add E2E tests to workflow

[f-necas]

🔧 E2E tests now works with Github actions.

⚠️ The default dump has been modified

• New group with a logo in Geonetwork : Barbie Inc.
• A record has been modified to get this group as organization.

💢 Known problems

• Tests who access to Geonetwork (login/editing parameters) takes a lot of time (~15/20 sec).

[github-actions]

Affected libs: api-repository, feature-catalog, feature-record, feature-router, feature-search, feature-map, feature-dataviz, feature-auth, common-domain, api-metadata-converter, feature-editor, ui-search, common-fixtures, util-shared, ui-elements, ui-catalog, ui-widgets, ui-inputs, ui-map, ui-dataviz, util-app-config,
Affected apps: datahub, metadata-editor, demo, webcomponents, search, map-viewer, datafeeder, metadata-converter, data-platform,

• 🚀 Build and deploy storybook and demo on GitHub Pages
• 📦 Build and push affected docker images

[jahow]

Thanks so much for tackling this! that must have been a lot of work. Having e2e tests running on the CI will add more constraints but hopefully it will help us keep a higher level of quality. 😎

I think it might be good to add a npm run e2e script (if it's not already there) and mention that having it pass is mandatory in the contributing guidelines.

Other than that I had several questions on your changes, see below!

[jahow]

I was hoping we could have a central place to put Cypress custom commands, instead of having to duplicate these in the different apps; or maybe from here you could import the commands from the datahub-e2e app?

[f-necas]

I didn't find a simple and clean way for the moment so I didn't implement it by now.

[jahow]

this can be done later, no worries