Some queries return null region values instead of the region value in the Steampipe table.

[JeffreyFudge]

Describe the bug
Some queries return a null in the region column, despite the fact that the AWS API (and thus the Steampipe table) have the value of "global".

This seems to be caused by the fact that some queries utilize "local.common_dimensions_qualifier_sql", which does not include region, and others utilize "common_dimensions_qualifier_global_sql", which includes region. These locals are out of variables.pp).

Query "iam_policy_custom_no_assume_role" is an example that does not leverage the global_sql and thus does not return a region.

As a result, findings can have an AWS region name, "global", or a null. It would seem that the region value in the API/table should always be returned and never set to null via omission.

Powerpipe version (powerpipe -v)
Example: v1.0.1

Steampipe version (steampipe -v)
Example: v1.0.1

Plugin version (steampipe plugin list)
Example: v1.2.0

To reproduce
Run the AWS Foundational Security Best Practices dashboard in Powerpipe and download the CSV file. Null values will be observed in the region column.

Expected behavior
I would expect to see the region value that is contained in the Steampipe table, and not a null.