[Azure Logs]: Azure Logs uses deprecated sanitize_options option for EventHub input

### Integration Name

Azure Logs [azure]

### Dataset Name

_No response_

### Integration Version

1.29.0

### Agent Version

8.19.6

### Agent Output Type

elasticsearch

### Elasticsearch Version

8.19.6

### OS Version and Architecture

Kubernetes

### Software/API Version

_No response_

### Error Message

legacy sanitization `sanitize_options` options are deprecated and will be removed in the 9.0 release; use the `sanitizers` option instead

### Event Original

_No response_

### What did you do?

Azure Logs integration is configured with the following input:
```
"activitylogs-azure-eventhub": {
"enabled": true,
"streams": {
"azure.activitylogs": {
"enabled": true,
"vars": {
"preserve_original_event": false,
"tags": [
"azure-activitylogs",
"forwarded"
],
"processors": "",
"sanitize_newlines": false,
"sanitize_singlequotes": true
}
}
}
}
```

### What did you see?

Relevant warning message fields:

### What did you expect to see?

No deprecation messages.

### Anything else?

We use this integration multiple times with slighty different configuration. We have an alert rule that watches for errors from the Azure Logs integration, so that we can quickly react to monitoring issues.
Filter: `event.dataset: "elastic_agent.filebeat" and component.type: "azure-eventhub" and (log.level: "error" or log.level: "warn")`

Every time the integration policy is updated, the deprecation warning gets logged. It is also logged once for each Azure Logs integration policy on the Elastic Agent when it is restarted. This always triggers our alert rule.