filebeat/azure/azureeventhub: upgrade azure-event-hubs-go and azure-storage-blob-go dependencies

[tetianakravchenko]

Proposed commit message

• WHAT: upgrade azure-event-hubs-go and azure-storage-blob-go dependencies
• WHY: Contains potential improvements to azure eventhub checkpoint handling, mentioned Intermittent PUT blob failed when updating checkpoint store Azure/azure-event-hubs-go#291 (comment)

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 added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Author's Checklist

• [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @tetianakravchenko? 🙏.
For such, you'll need to label your PR with:

• The upcoming major version of the Elastic Stack
• The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

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

[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

• Duration: 148 min 48 sec

❕ Flaky test report

No test was executed to be analysed.

🤖 GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
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 azure-eventhub-dependencies upstream/azure-eventhub-dependencies
git merge upstream/main
git push upstream azure-eventhub-dependencies

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
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 azure-eventhub-dependencies upstream/azure-eventhub-dependencies
git merge upstream/main
git push upstream azure-eventhub-dependencies

[zmoog]

I see this PR brings updates to a few modules:

• github.com/Azure/azure-amqp-common-go/v4 v4.2.0
• github.com/Azure/go-amqp v1.0.0
• github.com/Azure/azure-storage-blob-go v0.15.0
• github.com/Azure/azure-sdk-for-go v65.0.0

I ingested all the activity logs backlog from our dev subscription using Filebeat without issues. I also ran two Filebeats sharing the same event hub, and they could lease one partition each.

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
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 azure-eventhub-dependencies upstream/azure-eventhub-dependencies
git merge upstream/main
git push upstream azure-eventhub-dependencies