Change staging table to use 1 as unknown id instead of -1

[eiffel777]

For columns in the cloud staging tables related to the changes in #861 change the COALESCE statements to use 1 instead of -1.

Tests performed

Ran all tests in docker

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project as found in the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[jpwhite4]

Did the pre-populated table data change too?
[edit] I see that the pre-population action was already setting 1 as the unknown

[jpwhite4]

Where is the prepopulated data for these tables that have 'Unknown' hardcoded? I can't see it in the repo.
[edit] I see that it is set in the initialize_unknown_dimension_values action

[jpwhite4]

In the docs/cloud.md is says to run

php /usr/share/xdmod/tools/etl/etl_overseer.php -p jobs-common -p jobs-cloud-common -p ingest-resources

But I think that the jobs-cloud-common must be run after the ingest-resources otherwise the 'unknown' rows will not be populated properly.

[jpwhite4]

Need to update the comment for account_id column in configuration/etl/etl_tables.d/cloud_common/account.json

[jpwhite4]

Should not set the default person_id to 1 in configuration/etl/etl_tables.d/cloud_common/instance.json

[jpwhite4]

The comment on the modw_cloud.region.region_id column states

"Auto-increment relative to resource_id. We do not have unknown assets."

yet this table is populated with an 'unknown' row by the initialize_unknown_dimension_values.json. Which is correct?