[Fortinet Fortigate] Add url parsing error handling

[gogochan]

Proposed commit message

This PR introduces raw_url field for Fortinet Firewall if url parsing fails parsing
https://github.com/elastic/sdh-beats/issues/5691

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.
• I have verified that any added dashboard complies with Kibana's Dashboard good practices

Author's Checklist

• [ ]

How to test this PR locally

Related issues

Screenshots

[elasticmachine]

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

[elastic-vault-github-plugin-prod]

🚀 Benchmarks report

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

Expand to view

Data stream	Previous EPS	New EPS	Diff (%)	Result
log	1282.05	897.67	-384.38 (-29.98%)	💔

To see the full report comment with /test benchmark fullreport

[elasticmachine]

💔 Build Failed

• Buildkite Build
• Commit: af2f661

Failed CI Steps

• Check integrations fortinet_fortigate

History

• 💚 Build #22762 succeeded 918c6c6
• 💔 Build #22748 failed 635a550
• 💔 Build #22741 failed ed6a412

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
61.5% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube