package: use wolfi prefix

[v1v]

Motivation/summary

We have agreed to use apm-server-wolfi - "We want for users/customers to know the os flavor"

Let's wait for #12671 regardless

Checklist

• Update CHANGELOG.asciidoc
• Documentation has been updated

For functional changes, consider:

• Is it observable through the addition of either logging or metrics?
• Is its use being published in telemetry to enable product improvement?
• Have system tests been added to avoid regression?

How to test these changes

Locally running the package make goal

GENERATE_WOLFI_IMAGES=true \
  make package-snapshot

CI

If you create a feature branch in the upstream then the CI will do the rest, for instance I created feature/wolfi-name

• https://buildkite.com/elastic/apm-server-package/builds/2045#018fef35-92d2-411b-bd05-9677aa69910b/114-119

Related issues

[mergify]

This pull request does not have a backport label. Could you fix it @v1v? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-7.17 is the label to automatically backport to the 7.17 branch.
• backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit.

NOTE: backport-skip has been added to this pull request.

[kruskall]

@v1v can you resolve the merge conflicts ?

[mergify]

This pull request is now in conflicts. Could you fix it @v1v? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b feature/wolfi-name upstream/feature/wolfi-name
git merge upstream/main
git push upstream feature/wolfi-name