[Fortinet-Fortimail] Update fortinet fortimail

[robester0403]

Proposed commit message

[Fortinet_Fortimail] Documentation Update

generated new knowledge base file
generated new documentation

Please explain:

• WHAT: patterns used, algorithms implemented, design architecture, message processing, etc.
• WHY: the rationale/motivation for the changes

This text will be pasted into the squash dialog when the change is committed and will be
a long term historical record of the change to help future contributors understand the
change, please help them by making it clear and comprehensive, they may be you.

If the commit title is adequate to describe both of these things, The text here may be omitted
or replaced with "See title". The title of the PR will be used as the commit message title when
the merge is made and the "See title" marker will be removed if present.

The text here and the PR title will be subject to the PR review process.
-->

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]

💔 Build Failed

• Buildkite Build
• Commit: e4b35a8

Failed CI Steps

• :pipeline:⬆️ Upload Pipeline: .buildkite/pipeline.yml

History

• 💔 Build #38010 failed 1f86988

[elasticmachine]

Pinging @elastic/integration-experience (Team:Integration-Experience)