Build the wolfi image on CI

[lorenabalan]

Description

elastic-renovate recently bumped the sha for the base image of our wolfi docker image. Unfortunately that broke our image as apk has been stripped out, which requires a re-work of the Dockerfile. The regression slipped through the cracks because on CI we only build the simple Docker image (Dockerfile), not the wolfi one. Wolfi is only built at release time.

I tried a few different things to fix the new image, however it seems like it's a non-trivial amount of effort at this time, so we just reverted the bump.
For future reference, I tried using wget instead of curl, as well as installing curl and make via another build stage (from an alpine image, and copy it into the next stages). For example kept running into issues making make work

 > [builder 14/15] RUN make clean install:
0.116 rm -rf Jars.lock vendor/jars
0.158 script/environment
0.158 make: script/environment: No such file or directory
0.158 make: *** [Makefile:13: install] Error 127

Checklists

Pre-Review Checklist

• This PR does NOT contain credentials of any kind, such as API keys or username/passwords (double check crawler.yml.example and elasticsearch.yml.example)
• This PR has a meaningful title
• This PR links to all relevant GitHub issues that it fixes or partially addresses
  • If there is no GitHub issue, please create it. Each PR should have a link to an issue
• this PR has a thorough description
• Covered the changes with automated tests
• Tested the changes locally
• Added a label for each target release version (example: v0.1.0)
• Considered corresponding documentation changes
• Contributed any configuration settings changes to the configuration reference
• Ran make notice if any dependencies have been added

Related Pull Requests

#349

[mattnowzari]

LGTM 🚢 Thank you for adding this, this is excellent!

[github-actions]

💔 Failed to create backport PR(s)

The backport operation could not be completed due to the following error:
There are no branches to backport to. Aborting.

The backport PRs will be merged automatically after passing CI.

To backport manually run:
backport --pr 357 --autoMerge --autoMergeMethod squash

[mattnowzari]

💚 All backports created successfully

Status	Branch	Result
✅	0.4
✅	0.3

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation