Query config_enabled_all_regions should check all regions even if connections don't include all regions

[cbruno10]

Describe the bug
This query will not properly report if a configuration recorder is enabled in a region, as it will always report alarm even if a configuration recorder is setup correctly in that region, if the region is not included in the aws.spc connection file.

Steampipe version (steampipe -v)
v0.5.0

Plugin version (steampipe plugin list)
aws v0.18.0

To reproduce

• Create a configuration recorder in us-west-1 and configure it so:

  recording_group -> 'IncludeGlobalResourceTypes' = 'true'
  and recording_group -> 'AllSupported' = 'true'
  and status ->> 'Recording' = 'true'
  and status ->> 'LastStatus' = 'SUCCESS'
  

• Do not include us-west-1 in the regions argument in aws.spc
• Run the query

Expected behavior
The query should return ok instead of alarm

Additional context
Add any other context about the problem here.

[LalitLab]

https://turbothq.slack.com/archives/C01RN2G6KNK/p1621693183009700

[LalitLab]

There is a way to get it working but in that case, we have to change the table design to get the details of the configuration recorder for each enabled region.
It will be a simple change to include the parent hydrate function listAwsRegions to get the details of every region

similar to aws_ec2_instance_availability

[cbruno10]

I believe with connection tables, we could skip regions we aren't checking and inform the users properly - requested in turbot/steampipe#505

[misraved]

Closing this since the implementation was done here - turbot/steampipe#505