[cisco_meraki] Address the changes in Firmware MX18.101

[bhapas]

What does this PR do?

Cisco has changed the event_type for flow/ruleset logs, from flows to multiple other types. See the info box in the "Flows" paragraph in documentation, and the list of event_types This causes the logs-cisco_meraki.log pipeline to skip the logs-cisco_meraki.log-flows pipeline.

The flows pipeline also needs updating to correctly parse the new event types.

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.

How to test this PR locally

Related issues

• Closes cisco-meraki integration can't parse data #7387

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: 2023-08-16T05:01:54.472+0000

• Duration: 19 min 25 sec

Test stats 🧪

Test	Results
Failed	0
Passed	19
Skipped	0
Total	19

🤖 GitHub comments

Expand to view the 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% (2/2)	💚
Files	100.0% (9/9)	💚 3.453
Classes	100.0% (9/9)	💚 3.453
Methods	100.0% (65/65)	💚 8.362
Lines	98.046% (1104/1126)	👍 9.975
Conditionals	100.0% (0/0)	💚

[elasticmachine]

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

[elasticmachine]

Package cisco_meraki - 1.11.1 containing this change is available at https://epr.elastic.co/search?package=cisco_meraki