eset_protect: align batch_size config with ESET API spec

[ezzamo]

Proposed commit message

eset_protect: align batch_size with ESET API max (1000)

WHAT

This PR updates the eset_protect package configuration to align the batch_size (page size) setting with the maximum supported value documented in the ESET Connect API specification.

Concretely:

• Update batch_size description to reflect the API maximum (1000).
• Set the default batch_size to 1000 to avoid requesting an unsupported page size.

WHY

The ESET Connect API Swagger documentation for the relevant endpoints specifies a maximum page size of 1000. The package configuration previously allowed larger values. Although the documentation mentions that larger values are coerced to “1000”, it is best to align the configuration with the specification.

References:

• Automation / DeviceTasks (List tasks):
  https://eu.esetconnect.eset.systems/swagger/?urls.primaryName=Automation#/DeviceTasks/DeviceTasks_ListTasks
• Incident Management (Detection stream):
  https://eu.esetconnect.eset.systems/swagger/?urls.primaryName=Incident%20Management

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.
• I have verified that any added dashboard complies with Kibana's Dashboard good practices.

How to test this PR locally

From the integrations repo:

• cd packages/eset_protect
• elastic-package lint
• elastic-package build

upload it in kibana

Related issues

• N/A

[elasticmachine]

Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)

[ShourieG]

LGTM