[fortinet_fortigate] use YAML literal for script source

[andrewkroh]

What does this PR do?

All (indented) characters are considered to be content, including white space characters. This causes the source in the YAML to match the source in the ingest processor.

https://yaml.org/spec/1.2.2/#812-literal-style

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. No user facing changes. Just formatting.
• I have verified that Kibana version constraints are current according to guidelines.

Related

• Works around: Parser returns two documents instead of one goccy/go-yaml#374

[elasticmachine]

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

[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: 2023-05-30T20:26:46.833+0000

• Duration: 16 min 26 sec

Test stats 🧪

Test	Results
Failed	0
Passed	9
Skipped	0
Total	9

🤖 GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

[elasticmachine]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	100.0% (1/1)	💚
Files	100.0% (4/4)	💚
Classes	100.0% (4/4)	💚
Methods	100.0% (40/40)	💚 5.882
Lines	91.699% (1171/1277)	👎 -1.804
Conditionals	100.0% (0/0)	💚

[efd6]

Just confirming here and for the slack and infoblocks changes that the intention is to pick these up in later versions since they do not have changelog entries.

[andrewkroh]

Yes, that is indeed my indention 🤦 intention.