[cisco_secure_endpoint] fix template field indexing when next link is absent

[brijesh-elastic]

Proposed commit message

cisco_secure_endpoint: prevent updating fleet health status to degraded when HTTPJSON template value
evaluation failed and update the system test to correctly match hit counts.

This change bumps minimum kibana version to ^8.19.4 || ~9.0.7 || ^9.1.4 

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/cisco_secure_endpoint directory.
• Run the following command to run tests.

elastic-package test

Related issues

• Relates ssi: too many failing packages in daily job #15472

[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: c8228d7

cc @brijesh-elastic

[efd6]

Suggested commit message:

cisco_secure_endpoint: fix template field indexing when next link is absent

Don't updating fleet health status to degraded when HTTPJSON template
evaluation fails due to an absent metadata.links.next field.

[efd6]

nit

[efd6]

Suggested change

	- description: Prevent updating fleet health status to degraded.
	- description: Prevent updating fleet health status to degraded when no next link is present.