cisco,cisco_duo,cisco_ftd: fix event.outcome and event.type field values

[efd6]

What does this PR do?

This make field values agree with the allowable set according to ECS.

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

• Relates Packages using invalid values for fields according to ECS #3016

Screenshots

[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: 2022-04-06T22:32:37.182+0000

• Duration: 22 min 19 sec

Test stats 🧪

Test	Results
Failed	0
Passed	131
Skipped	0
Total	131

🤖 GitHub comments

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

• /test : Re-trigger the build.

[jsoriano]

Reopening as there seems to be still issues: https://beats-ci.elastic.co/blue/organizations/jenkins/Ingest-manager%2Fintegrations/detail/PR-3017/3/tests

test case failed: one or more problems with fields found in documents: [0] parsing field value failed: field "event.outcome"'s value "failed" is not one of the allowed values (failure, success, unknown)