The `is_logging` column of the `aws_cloudtrail_trail` table returns `null` for organization trails when the value is 'true' in the AWS CLI

[misraved]

Describe the bug The is_logging column of the aws_cloudtrail_trail table returns null for organization trails when the value is 'true' in the AWS CLI. In this PR, we fixed the cloudtrails at an account level but missed out on fixing the issue for organization trails.

Steampipe version (steampipe -v) Example: v0.14.6

Plugin version (steampipe plugin list) Example: v0.63.0

To reproduce run select * from aws_cloudtrail_trail, or a more targeted query to pull back information about whether a cloudtrail is currently logging, and compare that data to AWS CLI output or console information. Here's an example CLI command aws cloudtrail get-trail-status --name MyTargetTrail --region us-east-1

Expected behavior The value from the AWS CLI and the Steampipe CLI should remain consistent.

[github-actions[bot]]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.

[github-actions[bot]]

'This issue was closed because it has been stalled for 60 days with no activity.'

[misraved]

@ParthaI Could you please add details on the approach and the challenges in implementing the fix for this bug?

[github-actions[bot]]

'This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days.'

[github-actions[bot]]

'This issue was closed because it has been stalled for 90 days with no activity.'