cisco_ise: map cisco_ise.log.avpair.task_id as keyword

[efd6]

What does this PR do?

In most documented cases cisco_ise.log.avpair.task_id appears to be a decimal
numeric value. However, in the wild hex, numerical and UUID values appear to
exist so map as a keyword.

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.

Author's Checklist

• [ ]

How to test this PR locally

Related issues

• Closes cisco_ise wrong field-type of field cisco_ise.log.avpair.task_id #4075

Screenshots

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2022-09-13T01:08:13.926+0000

• Duration: 14 min 6 sec

Test stats 🧪

Test	Results
Failed	0
Passed	90
Skipped	0
Total	90

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[elasticmachine]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	100.0% (1/1)	💚
Files	100.0% (17/17)	💚 2.537
Classes	100.0% (17/17)	💚 2.537
Methods	100.0% (181/181)	💚 9.77
Lines	99.835% (3019/3024)	👍 8.934
Conditionals	100.0% (0/0)	💚

[elasticmachine]

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)

[Bernhard-Fluehmann]

Thanks for fixing. I have manually changed the processor and mapping as well and it works fine so far.

[efd6]

/test