feat: use esbuild when possible for project builds

[shyim]

Right now shopware-cli project ci uses the traditional steps like build-administration.sh and build-storefront.sh

Since a while we support esbuild for building extensions much faster without access to the Shopware source code. To adopt this for building multiple extensions, we know split the extensions:

• ESBuild compatible admin/storefront now will always be build with esbuild.
• Any non-compatible extension will use the regular complication

So we have the best of both worlds. Some extensions build faster and which are not compatible use the regular setup.

Some benchmarks:

Project: All extensions have esbuild support.

• shopware project ci (current version): 1 minute build time.
• shopware project ci (this branch): 29 seconds build time.

I think the improvement can be better seen in CI like GitHub Actions with limited amount of resources. My machine has 16 cores, 128gb memory, little bit overkill to compare, but still 2x faster than the previous version.

[github-actions]

Qodana for Go

It seems all right 👌

No new problems were found according to the checks applied

💡 Qodana analysis was run in the pull request mode: only the changed files were checked
☁️ View the detailed Qodana report

Contact Qodana team

Contact us at [email protected]

• Or via our issue tracker: https://jb.gg/qodana-issue
• Or share your feedback: https://jb.gg/qodana-discussions