[Beyondtrust PRA] Change session_owner type from keyword to boolean and Update documentation

[moxarth-rathod]

Proposed commit message

beyondtrust_pra: change session_owner type from keyword to boolean

It was incorrectly mapped as keyword.

Also, remove GCP from the documentation, this integration uses CEL-only.

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

How to test this PR locally

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

elastic-package test

Related issues

• Closes [Beyondtrust PRA] fix session_owner type and update documentation #18677

[github-actions]

Vale Linting Results

Summary: 2 warnings, 1 suggestion found

⚠️ Warnings (2)

File	Line	Rule	Message
packages/beyondtrust_pra/_dev/build/docs/README.md	27	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/beyondtrust_pra/docs/README.md	27	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.

💡 Suggestions (1)

File	Line	Rule	Message
packages/beyondtrust_pra/docs/README.md	103	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.

---

The Vale linter checks documentation changes against the Elastic Docs style guide.

To use Vale locally or report issues, refer to Elastic style guide for Vale.

[elasticmachine]

Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)

[elastic-vault-github-plugin-prod]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: e09236a

History

• 💚 Build #41722 succeeded c0b2da8

cc @moxarth-rathod

[efd6]

Is there a backing issue for this?

[moxarth-rathod]

Is there a backing issue for this?

Created an issue: #18677

[efd6]

Note change in proposed commit message.

Also, in looking at this, the initial json processor has an on_failure processor. I think that it should probably not since if it fails, nothing further will be successful. Not for this PR.

/cc @kcreddy

[elastic-vault-github-plugin-prod]

Package beyondtrust_pra - 0.4.0 containing this change is available at https://epr.elastic.co/package/beyondtrust_pra/0.4.0/