[cisco_nexus]: remove redundant nested repeat operator

[pkoutsovasilis]

Proposed commit message

After tackling this issue, a respective PR was created to elastic-package to mainstream the detection of similar warnings. Thus this PR fixes the following similar to the former issue regex-related warning for cisco_nexus

detected ingest pipeline warnings: 1: regular expression has redundant nested repeat operator * /(?:^(?:(?:.*)(?:\s*)?(?i)interface)(?:\s*)(?<DATA:cisco_nexus.log.interface.name>.*?) is up in mode (?<DATA:cisco_nexus.log.interface.mode>.*?)$)|(?:^(?:(?:.*)(?:\s*)?(?i)interface)(?:\s*)(?<DATA:cisco_nexus.log.interface.name>.*?) is (?:.*)$)|(?:^(?:(?:.*)(?:\s*)?(?i)interface)(?:\s*)(?<DATA:cisco_nexus.log.interface.name>.*?), operational speed changed to (?<DATA:cisco_nexus.log.operational.speed>.*?)$)|(?:^(?:(?:.*)(?:\s*)?(?i)interface)(?:\s*)(?<DATA:cisco_nexus.log.interface.name>.*?), operational duplex mode changed to (?<DATA:cisco_nexus.log.operational.duplex_mode>.*?)$)|(?:^(?:(?:.*)(?:\s*)?(?i)interface)(?:\s*)(?<DATA:cisco_nexus.log.interface.name>.*?), operational Receive Flow Control state changed to (?<DATA:cisco_nexus.log.operational.receive_flow_control_state>.*?)$)|(?:^(?:(?:.*)(?:\s*)?(?i)interface)(?:\s*)(?<DATA:cisco_nexus.log.interface.name>.*?), operational Transmit Flow Control state changed to (?<DATA:cisco_nexus.log.operational.transmit_flow_control_state>.*?)$)|(?:^(?:(?:.*)(?:\s*)?(?i)interface)(?:\s*)(?<DATA:cisco_nexus.log.interface.name>.*?), (?:.*)$)/

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

N/A

How to test this PR locally

Related issues

N/A

Screenshots

N/A

[elasticmachine]

Pinging @elastic/sec-deployment-and-devices (Team:Security-Deployment and Devices)

[elasticmachine]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[jrmolin]

🤷

[dwhyrock]

Data stream	Previous EPS	New EPS	Diff (%)	Result
log	1697.79	1275.51	-422.28 (-24.87%)	💔

Do we need to be concerned about the performance report?

[pkoutsovasilis]

/test benchmark fullreport

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 05295cf

History

• 💚 Build #10412 succeeded 2d4c1abb4c25f4b439e0743279e2b82552926de6
• 💚 Build #10357 succeeded 04029135137b1a4ec346c711ec59924683c5dac2
• 💚 Build #10353 succeeded 04029135137b1a4ec346c711ec59924683c5dac2

cc @pkoutsovasilis

[elastic-sonarqube]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube