[cisco_meraki] Update event.type and event.category of anyconnect_vpn_connect

[brijesh-elastic]

Proposed commit message

cisco_meraki: Harmonise `event.type` and `event.category` treatment of anyconnect_vpn_connect with client_vpn_connect events 

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

elastic-package test

Related issues

• Closes cisco_meraki: harmonise event.type and event.category treatment of anyconnect_vpn_connect and client_vpn_connect #14260

[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

[efd6]

This is nice for consistency, but it would break people who are searching on "anyconnect_vpn_connect".

I think we will need to leave this the same.

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 68c4025

History

• 💚 Build #29293 succeeded 8cfaad1

cc @brijesh-elastic

[efd6]

Thanks

[elastic-vault-github-plugin-prod]

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