cisco_{asa,ftd}: fix handling of 302020 messages

[efd6]

What does this PR do?

This fixes the handling of message type 302020 which was being incorrectly characterised as a termination event rather than a start event.

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

• Updates cisco_asa, cisco_ftd: wrong classification of event 302020 #4199

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-19T12:12:54.892+0000

• Duration: 19 min 2 sec

Test stats 🧪

Test	Results
Failed	0
Passed	49
Skipped	0
Total	49

🤖 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% (2/2)	💚 2.679
Classes	100.0% (2/2)	💚 2.679
Methods	100.0% (35/35)	💚 10.241
Lines	76.28% (2666/3495)	👎 -15.161
Conditionals	100.0% (0/0)	💚

[elasticmachine]

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

[djptek]

"event.action": "flow-creation" looks OK in the test results

LGTM

[elasticmachine]

🚀 Benchmarks report

Package cisco_asa 👍(0) 💚(0) 💔(1)

Expand to view

Data stream	Previous EPS	New EPS	Diff (%)	Result
log	268.82	168.32	-100.5 (-59.71%)	💔

Package cisco_ftd 👍(1) 💚(0) 💔(0)

To see the full report comment with /test benchmark fullreport