[cisco_asa] Add support for IPv6 parsing in 302xxx messages

[mjwolf]

Proposed commit message

In 302xxx messages, add properly parse IPv6 addresses. Previously, the address could be improperly parsed into interface, as both use colon seperators. This reorders the parsing to do IPv6 first, so that these addresses will be correctly parsed, while still parsing the interface if the field isn't IPv6.

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

[elasticmachine]

Pinging @elastic/integration-experience (Team:Integration-Experience)

[elastic-vault-github-plugin-prod]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 1f20ccc

History

• 💚 Build #32625 succeeded b026d83
• 💚 Build #32604 succeeded e4dc0d2
• 💚 Build #32563 succeeded e01ee9c
• 💚 Build #32523 succeeded bd92e6a