fix: update azeventhubs v2 import in v2_input_test.go

[strawgate]

Summary

• Fix broken import in v2_input_test.go after the azeventhubs SDK v2 upgrade (x-pack/filebeat: upgrade azeventhubs SDK to v2.0.2 #49867)
• Update import path from azeventhubs to azeventhubs/v2
• Update Offset field values from int64 to string (v2 breaking change)

This was missed in #49867 and is currently breaking lint CI on all open PRs (e.g. #50022).

Test plan

• Lint CI passes (the only change is fixing the broken import/type)
• go vet ./x-pack/filebeat/input/azureeventhub/... passes (verified locally)

🤖 Generated with Claude Code

[github-actions]

🤖 GitHub comments

Just comment with:

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

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @strawgate? 🙏.
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-8./d is the label to automatically backport to the 8./d branch. /d is the digit
• backport-active-all is the label that automatically backports to all active branches.
• backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
• backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 2a9f82ed-97ab-4553-8c9d-8b524a53dcb2

📥 Commits

Reviewing files that changed from the base of the PR and between df60c84 and 89be972.

📒 Files selected for processing (1)

• x-pack/filebeat/input/azureeventhub/v2_input_test.go

---

📝 Walkthrough

Walkthrough

The test file imports the v2 version of the Azure SDK for Event Hubs. The TestProcessReceivedEventsUpdatesProcessingTimeOnce test updates mock ReceivedEventData objects to use string values ("0", "1", "2") for the Offset field instead of numeric values, reflecting the type changes in the v2 API. The test logic and assertions remain unchanged. No public entity declarations were modified.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

• 🛠️ Update Documentation: Commit on current branch
• 🛠️ Update Documentation: Create PR

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[elasticmachine]

Pinging @elastic/obs-ds-hosted-services (Team:obs-ds-hosted-services)

[zmoog]

Ouch, what a failure. Thanks for fixing it, @strawgate. On it.

[zmoog]

This was missed in #49867 and is currently breaking lint CI on all open PRs (e.g. #50022).

I was curious to know why CI didn't catch this. It turns out the failure was caused by the interplay between two PRs, both of which were fine in isolation:

• I merged azure-eventhub v2: fix processingTime input metric #49864, which added new tests (still using ints for offsets).
• I merged x-pack/filebeat: upgrade azeventhubs SDK to v2.0.2 #49867, which upgraded to azeventhubs/v2, where offsets are handled as strings.

Staying synced with main (or using the merge queue) would have avoided this inconsistency.