cisco_asa: fix handling of non-canonical 113005 messages

[efd6]

What does this PR do?

This relaxes the parsing of 113005 messages that do not conform to the documented format but appear in the wild.

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

• Note that this actually tightens the format requirement on usernames since they must now actually satisfy the Cisco username syntax while before any non-space would be accepted.

How to test this PR locally

Related issues

• Fixes cisco_asa: failing to parse non-canonical 113005 message #4185

Screenshots

[elasticmachine]

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

[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-12T10:18:26.575+0000

• Duration: 16 min 52 sec

Test stats 🧪

Test	Results
Failed	0
Passed	30
Skipped	0
Total	30

🤖 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% (1/1)	💚
Classes	100.0% (1/1)	💚
Methods	100.0% (18/18)	💚
Lines	83.827% (1555/1855)	❕
Conditionals	100.0% (0/0)	💚

[kcreddy]

LGTM 👍🏼