[ti_threatq] fix template evaluation to prevent updating fleet health status to degraded

[brijesh-elastic]

Proposed commit message

ti_threatq: don't update fleet health status to degraded pagination completes

It also corrects the output response JSON in the system test config rules. I've verified the
response structure against the live API.

This change bumps minimum Kibana version to ^8.19.4 || ~9.0.7 || ^9.1.4 and adds
`do_not_log_failure: true` in set transforms to avoid updating
fleet health status to degraded.

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

• Clone integrations repo.
• Install elastic package locally.
• Start elastic stack using elastic-package.
• Move to integrations/packages/ti_threatq directory.
• Run the following command to run tests.

elastic-package test

Related issues

[elasticmachine]

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

[elastic-vault-github-plugin-prod]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 4ec4d8a

cc @brijesh-elastic

[elastic-vault-github-plugin-prod]

Package ti_threatq - 1.37.0 containing this change is available at https://epr.elastic.co/package/ti_threatq/1.37.0/