Cisco Secure Email Gateway | Update grok pattern to extract additional fields

[kcreddy]

What does this PR do?

Fixes existing grok pattern for Cisco Secure Email Gateway to match additional fields.

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.

[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-11-30T16:44:27.301+0000

• Duration: 16 min 8 sec

Test stats 🧪

Test	Results
Failed	0
Passed	23
Skipped	0
Total	23

🤖 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% (1/1)	💚
Files	83.333% (10/12)	👎 -16.667
Classes	83.333% (10/12)	👎 -16.667
Methods	89.286% (50/56)	👎 -10.714
Lines	85.69% (497/580)	👎 -10.581
Conditionals	100.0% (0/0)	💚

[elasticmachine]

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