[Fortinet] Deprecate original integration & change logfile to filestream

[legoguy1000]

What does this PR do?

• Deprecate original Fortinet integration
• Swap the logfile legacy input for the filestream input

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

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-15T22:13:59.319+0000

• Duration: 26 min 52 sec

Test stats 🧪

Test	Results
Failed	0
Passed	60
Skipped	0
Total	60

🤖 GitHub comments

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

• /test : Re-trigger the build.

[efd6]

/test

[elasticmachine]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	100.0% (8/8)	💚
Files	100.0% (14/14)	💚 2.868
Classes	100.0% (14/14)	💚 2.868
Methods	92.029% (127/138)	👍 2.803
Lines	90.741% (2499/2754)	👎 -0.001
Conditionals	100.0% (0/0)	💚

[legoguy1000]

@efd6 comments resolved.

[efd6]

/test

[efd6]

/test

[efd6]

/test

[elasticmachine]

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)

[andrewkroh]

I think changing from log to filestream will cause problems for users because they will lose their existing state. Much of this is discussed in #2518. I think we should hold off on this change given the packages are GA. We'll cover making the change with #2518.

So I think the filestream changes should be reverted.

[legoguy1000]

@andrewkroh Will do.

[legoguy1000]

GTG