Fix E2E test failures

[jahow]

Description

This PR tweaks E2E tests further. Issues fixed are:

• sometimes the custom thesauri (GEMEt and INSPIRE themes) in the init step were pushed to GN, but then the thesauri would be reset and the "regions" thesauri would be pushed instead; I added a delay before pushing the custom thesauri and it always works now!
• I also added a print of the indexation errors happening in the init step, so that we can make sure that indexation happens exactly like it does locally (it wasn't the case before the above change)
• I added a dependency from the metadata-editor E2E to datahub E2E because if the editor tests pass first they change the records so that the datahub tests will fail after that; obviously this is not ideal (it shows that the datahub tests are too sensitive) but we can live with that for now

Architectural changes

none

Quality Assurance Checklist

• Commit history is devoid of any merge commits and readable to facilitate reviews
• If new logic ⚙️ is introduced: unit tests were added
• If new user stories 🤏 are introduced: E2E tests were added
• If new UI components 🕹️ are introduced: corresponding stories in Storybook were created
• If breaking changes 🪚 are introduced: add the breaking change label
• If bugs 🐞 are fixed: add the backport <release branch> label
• The documentation website 📚 has received the love it deserves

[github-actions]

Affected libs: feature-map, feature-dataviz, feature-record, feature-router,
Affected apps: metadata-editor, datahub, demo, webcomponents, search, map-viewer,

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

[github-actions]

📷 Screenshots are here!

[coveralls]

coverage: 84.145% (+1.2%) from 82.94%
when pulling 4314f0c on fix-e2e-test-again
into caf9e4e on main.

[LHBruneton-C2C]

Thanks for taking the time to fix the e2e test!