[netskope] Fix: dropping event due to new response from Netskope API.

[vinit-chauhan]

What does this PR do?

In the Netskope response previously the response had true as a value for the field netskope.events.user.generated. Now the API response is updated to send yes instead, resulting in the pipeline failure.

In this PR we have added conversions for true/false and yes/no to all the boolean fields so that such API changes for other fields can also be handled.

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

Clone integrations repo.
Install elastic-package locally.
Start elastic stack using elastic-package.
Move to integrations/packages/netskope directory.
Run the following command to run tests.
elastic-package test

Related issues

• Closes [Netskope] Dropping event due to parsing error #3084

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-04-15T15:31:33.388+0000

• Duration: 14 min 53 sec

Test stats 🧪

Test	Results
Failed	0
Passed	110
Skipped	0
Total	110

🤖 GitHub comments

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

• /test : Re-trigger the build.

[andrewkroh]

/test

[elasticmachine]

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

[andrewkroh]

/test

[andrewkroh]

/test