Change page_size and batch_size manifest variable type from text to integer - part 1

[kcreddy]

Proposed commit message

Change page_size and batch_size manifest variable type from text to integer - part 1

Several integrations declare page_size or batch_size manifest variables
with type: text when the value is always a positive integer. Fleet
performs no numeric validation on text fields, so a user can set these
to arbitrary strings. Changing to type: integer ensures Fleet rejects
non-numeric input.

Relates https://github.com/elastic/integrations/issues/19248

[git-generate]
for pkg in abnormal_security armis authentik aws_securityhub cyberark_epm; do
  find "packages/$pkg/" -type f -name manifest.yml \
    -exec perl -i -0pe 's/(name: (?:page_size|batch_size)\n\s+)type: text/$1type: integer/g' {} +
done
for pkg in $(git diff --name-only packages/ | cut -d/ -f1,2 | sort -u); do
  (
    cd "$pkg"
    elastic-package changelog add \
      --description "Change page_size/batch_size variable type from text to integer for Fleet input validation." \
      --type bugfix --next patch \
      --link "https://github.com/elastic/integrations/pull/19249"
  )
done

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

Related issues

• Relates Numeric page_size / batch_size manifest variables incorrectly declared as type: text #19248

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 044a9da

[infra-vault-gh-plugin-prod]

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