[PFsense] Fix Redundant Grok pattern

[legoguy1000]

What does this PR do?

Fix redundant Grok Pattern that causes "warning" messages in Elasticsearch logs.

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

• Closes pfsense: Redundant regex operation error in Elasticsearch #3955

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-08-08T13:01:56.958+0000

• Duration: 18 min 2 sec

Test stats 🧪

Test	Results
Failed	0
Passed	45
Skipped	0
Total	45

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[r00tu53r]

LGTM

[r00tu53r]

/test

[elasticmachine]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	100.0% (1/1)	💚
Files	88.889% (8/9)	👎 -8.249
Classes	88.889% (8/9)	👎 -8.249
Methods	91.667% (55/60)	👍 2.404
Lines	88.217% (554/628)	👎 -2.424
Conditionals	100.0% (0/0)	💚

[legoguy1000]

@r00tu53r Ready to merge