IBX-10495: [Backport] Included Elasticsearch 8 on CI

[micszo]

🎫 Issue	IBX-10495

Related PRs:

• IBX-10495: [Backport] Adjusted prepare project script for use with ES 8 (4.6) ci-scripts#123

Description:

Backport of #54 to 4.6.

Added new file for Elasticsearch 8 (8.19.9).

Fixed Dockerfiles for Node (12, 14, 16, 18) to resolve issues with building and testing images on CI.

For QA:

Please see:

• IBX-10495: Included Elasticsearch 8 on CI (4.6) headless#237
• IBX-10495: Included Elasticsearch 7 & 8 on CI (4.6) experience#570
• IBX-10495: Included Elasticsearch 8 on CI (4.6) commerce#1649

Documentation:

[kossuth-wt]

@micszo is there a reason why yarn@stable is used in ‎php/Dockerfile-node18? (The other dockerfiles have yarn@1.22.22). This caused in one of our projects gitlab CI fail because yarn@4.12.0 was fetched as the "stable", but in the project "current global version of Yarn is 1.22.22".

We use ghcr.io/ibexa/docker/php:8.3-node18 as our PHP image. We had to add this to our Dockerfile-app to make the project use yarn 1.22.22 and not fail on install.

RUN apt-get update -q -y \
&& apt-get install -q -y --no-install-recommends gnupg \
&& curl -sL https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add - \
&& echo "deb https://dl.yarnpkg.com/debian/ stable main" | tee /etc/apt/sources.list.d/yarn.list \
&& sudo apt-get update && sudo apt-get install yarn=1.22.22-1 \
&& rm -rf /var/lib/apt/lists/*

https://doc.ibexa.co/en/latest/getting_started/requirements/#asset-manager also states 1.x version is used.

[micszo]

Hi @kossuth-wt, this wasn't intended and must have slipped in unnoticed during development. I will fix this. Thanks for reporting!

[kossuth-wt]

@micszo Another thing is that two dockerfiles use npm install and two uses corepack to install yarn, that also might worth a look.