chore: bump elastic-package to v0.25.0

[mdelapenya]

What does this PR do?

It bumps elastic-package to 0.25.0

Why is it important?

See #1720

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have run the Unit tests (make unit-test), and they are passing locally
• I have run the End-2-End tests for the suite I'm working on, and they are passing locally
• I have noticed new Go dependencies (run make notice in the proper directory)

Author's Checklist

• [ ]

Related issues

• Closes Bump elastic-package to 0.25 #1720

[mergify]

This pull request is now in conflict. Could you fix it @mdelapenya? 🙏
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 bump-elastic-package upstream/bump-elastic-package
git merge upstream/master
git push upstream bump-elastic-package

[mergify]

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

• v./d./d./d is the label to automatically backport to the 7./d branch. /d is the digit
  NOTE: backport-skip has been added to this pull request.

[mdelapenya]

Sending to 7.16 to verify the resolution. If CI passes we should:

• forward port to master
• backport to 7.15

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2021-10-26T08:48:38.837+0000

• Duration: 39 min 30 sec

• Commit: 4bd98a9

Test stats 🧪

Test	Results
Failed	0
Passed	98
Skipped	0
Total	98

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[mdelapenya]

In https://beats-ci.elastic.co/blue/organizations/jenkins/e2e-tests%2Fe2e-testing-mbp/detail/PR-1721/2/pipeline/219 we can see that the fix is effective, and the runtime deps are provisioned by elastic-package: