[azure-eventhub] Update sdk/messaging/azeventhubs to v1.3.0

[zmoog]

Proposed commit message

Upgrade the sdk/messaging/azeventhubs package to the latest stable version v1.3.0.

This package is the core library of the modern Event Hub SDK we use in the azure-eventhub input v2. From v1.2.1 to v1.3.0 we get several bug fixes and a new TCP proxies with AMQP feature.

Author's Checklist

• Run a input v2 smoke test ingesting activity logs

How to test this PR locally

# x-pack/filebeat/modules.d/azure.yml
- module: azure
  # All logs
  activitylogs:
    enabled: true
    var:
      # eventhub name containing the activity logs, overwrite he default value if the logs are exported in a different eventhub
      eventhub: "logs"
      # consumer group name that has access to the event hub, we advise creating a dedicated consumer group for the azure module
      consumer_group: "$Default"
      # the connection string required to communicate with Event Hubs, steps to generate one here https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-get-connection-string
      connection_string: '${EVENTHUB_CONNECTION_STRING:""}'
      # the name of the storage account the state/offsets will be stored and updated
      storage_account: '${EVENTHUB_STORAGE_ACCOUNT:""}'
      # the name of the storage account container you would like to store the offset information in.
      # storage_account_container: ""
      # the storage account key, this key will be used to authorize access to data in your storage account
      storage_account_key: '${EVENTHUB_STORAGE_ACCOUNT_KEY:""}'
      # the connection string required to communicate with the storage account, steps to generate one here https://docs.microsoft.com/en-us/azure/storage/common/storage-account-keys-manage?tabs=azure-portal
      storage_account_connection_string: '${EVENTHUB_STORAGE_ACCOUNT_CONNECTION_STRING:""}'
      # the processor version to use, v1 is the legacy processor and v2 is the new processor
      processor_version: v2

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @zmoog? 🙏.
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.

[elasticmachine]

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

[zmoog]

Hey @elastic/beats-tech-leads, the PR is ready for your review! 🙇