Replace Markdown Navigation with Links Panel

[robester0403]

Proposed commit message

Replaced markdown navigation in the cisco_ise, fortinet_fortimail, and osquery dashboards with more user-friendly link panels.

Updated the supported Kibana version for the fortinet_fortimail integration to 8.11.0^.

Removed the single redundant navigation link for the imperva integration dashboard.

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

Built links panels for osquery and Cisco ISE to match the marked down before exactly in their kibana version.
Removed redundant information and links for imperva dashboard as discussed in #14812
Reviewed change logs and updated support for fortinet_fortimail to support kibana 8.11.0^ so we can add links panels.
Added links panels to fortinet_fortimail dashboard.

How to test this PR locally

Clone integrations repo.
Install elastic package locally.
Start elastic stack using elastic-package.
Install and test the packages locally with elastic-package
Go to dashboards and view the changes

Related issues

Closes #14812

Screenshots

Cisco ISE before:

Cisco ISE after

Osquery before:

Osquery after:

Fortinet Mail before:

Fortinet Mail after:

Imperva before. The integrations link is a relative link leading to the install integration page that can't be done in links panels. There is no navigation needed since it is only 1 dashboard page:

Imperva after:

[elastic-vault-github-plugin-prod]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[andrewkroh]

Why is there an Imperva tag is osquery?

[robester0403]

I removed the problem files, which came from trying to batch export all the dashboards. It should be fine now. Thanks!

[andrewkroh]

Do these tag files need to be committed? I'm not actually sure how it works, but I thought that a kibana/tags.yml specified what tags to apply the dashboards, but we didn't need to commit the actual saved objects.

[robester0403]

While not completely sure, I deleted the tags and try to build the packages without the tags using elastic-package build.

It fails for all three of the packages that had tags added (cisco_ise, fortinet_fortimail, and osquery).

[elasticmachine]

💔 Build Failed

• Buildkite Build
• Commit: 1d4c1cc

Failed CI Steps

• Check integrations osquery

History

• 💔 Build #30126 failed 8b36783
• 💚 Build #30039 succeeded f3b779a
• 💔 Build #30038 failed 7c55c85

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

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

See analysis details on SonarQube