Do not fail cleanup-dbt-resources workflow if databases do not exist

[jeancochrane]

This PR fixes a bug in the cleanup-dbt-resources workflow that causes it to fail in the (expected) case where it attempts to clean up a database that has not been created by CI. We adjust the underlying cleanup_dbt_resources.sh script to continue execution in cases where the aws glue delete-database command returns a nonzero status with EntityNotFoundException in the output.

Closes #104.

Local testing

I tested this PR locally since it would be a bit of a pain to test on CI. I tested two cases:

1. Sample output in the case of 404s: I ran the script against the dev target without building any models, and confirmed that it completed execution
2. Sample output in the case of unexpected error: I adjusted the script to add a bogus --asdf flag to the aws glue delete-database call, and confirmed that it stopped execution

Select a dropdown below to see the corresponding test output.

Sample output in the case of 404s

(venv) jecochr@21CCAO-LAPTOP54:~/code/data-architecture/dbt$ ../.github/scripts/cleanup_dbt_resources.sh dev
Deleting the following schemas from Athena:

"dev_jecochr_census"
"dev_jecochr_default"
"dev_jecochr_location"
"dev_jecochr_model"
"dev_jecochr_proximity"
"dev_jecochr_reporting"
"dev_jecochr_rpie"

An error occurred (EntityNotFoundException) when calling the DeleteDatabase operation: Database dev_jecochr_census not found.
Continuing execution due to expected 404 response.

An error occurred (EntityNotFoundException) when calling the DeleteDatabase operation: Database dev_jecochr_default not found.
Continuing execution due to expected 404 response.

An error occurred (EntityNotFoundException) when calling the DeleteDatabase operation: Database dev_jecochr_location not found.
Continuing execution due to expected 404 response.

An error occurred (EntityNotFoundException) when calling the DeleteDatabase operation: Database dev_jecochr_model not found.
Continuing execution due to expected 404 response.

An error occurred (EntityNotFoundException) when calling the DeleteDatabase operation: Database dev_jecochr_proximity not found.
Continuing execution due to expected 404 response.

An error occurred (EntityNotFoundException) when calling the DeleteDatabase operation: Database dev_jecochr_reporting not found.
Continuing execution due to expected 404 response.

An error occurred (EntityNotFoundException) when calling the DeleteDatabase operation: Database dev_jecochr_rpie not found.
Continuing execution due to expected 404 response.

Sample output in the case of unexpected error

(venv) jecochr@21CCAO-LAPTOP54:~/code/data-architecture/dbt$ ../.github/scripts/cleanup_dbt_resources.sh dev
Deleting the following schemas from Athena:

"dev_jecochr_census"
"dev_jecochr_default"
"dev_jecochr_location"
"dev_jecochr_model"
"dev_jecochr_proximity"
"dev_jecochr_reporting"
"dev_jecochr_rpie"

usage: aws [options] <command> <subcommand> [<subcommand> ...] [parameters]
To see help text, you can run:

  aws help
  aws <command> help
  aws <command> <subcommand> help

Unknown options: --asdf
xargs: bash: exited with status 255; aborting

[dfsnow]

@jeancochrane Nice fix! I should've merged this before Billy's PR since it caused exactly the error described here.