Cumulus upgrade to v16.1.1

@jsrikish, @krisstanton, and I went over the Cumulus release notes from the version immediately following 13.4.0 (our current version) through 16.1.1. Offhand, it appears that our upgrade path should be relatively smooth. Here are the pertinent points we extracted from the various release notes:

Pull the latest code from our main branch and create a new branch named cumulus-upgrade-16.1.1
v14.0.0: No notable Terraform changes required
v14.1.0:
- [x] We manually upgraded PostgreSQL to v11 at the beginning of the year, but the latest "point" version at that time was 11.13. It is currently 11.18 (and AWS automatically upgrades point versions for us), so we will bump the value of engine_version in app/stacks/rds-cluster/main.tf to match.
v15.0.0
- [x] Upgrade to latest Node 16.x version (set version inside the .nvmrc file)
- [x] Add the following block above the module "cumulus" block within app/stacks/cumulus/main.tf:
```
data "aws_ecr_repository" "async_operation" {
name = "async_operations"
}
```
- [x] Add the following inside of the module "cumulus" block within app/stacks/cumulus/main.tf (note that v15.0.0 sets the version number to 44, but the release notes for v16.1.1 bump it to 47):
```
async_operation_image = "${data.aws_ecr_repository.async_operation.repository_url}:47"
```
v15.0.1: nothing to do
v15.0.2: nothing to do
v15.0.3: nothing to do
v15.0.4: nothing to do
v16.0.0: nothing to do (bump of version for async_operation_image is subsumed by change noted in v16.1.1)
v16.1.1:
- [x] Add the following inside of the module "cumulus" block within app/stacks/cumulus/main.tf
```
orca_api_uri = module.orca.orca_api_deployment_invoke_url
orca_lambda_copy_to_archive_arn = module.orca.orca_lambda_copy_to_archive_arn
orca_sfn_recovery_workflow_arn = module.orca.orca_sfn_recovery_workflow_arn
```
- [x] In app/stacks/cumulus/main.tf, find module.orca.orca_lambda_copy_to_glacier_arn and change the name to module.orca.orca_lambda_copy_to_archive_arn
- [x] Run bin/set-cumulus-version.sh 16.1.1
- [x] In app/stacks/cumulus/orca.tf, change the version of the orca zip file (value of source property inside module "orca") from v6.0.3 to v8.0.1 (although this ORCA version upgrade is not explicitly stated in the Cumulus v16.1.1 release notes, there is a note that the example file was updated to use ORCA v8.0.1, so we're keeping things aligned with the example)
ORCA v8.0.1
- [x] Update the bucket policy for your system-bucket to allow load balancer to post server access logs to the bucket.
- [x] In app/stacks/rds-cluster/main.tf, add this new block:
```
resource "random_password" "db_user_password" {
length  = 50
upper   = true
lower   = true
number  = true
special = true
}
```
- [x] In app/stacks/rds-cluster/main.tf, change this line:
```
rds_user_password        = random_password.db_password.result
```
  to this:
```
rds_user_password        = random_password.db_user_password.result
```
  (i.e., on the right side of the assignment, change db_password to db_user_password, which is the name of the new block added in the previous point)

After making all of the file changes above, do the following in a sandbox deployment:

[x] Run make all-init (this might take a fair bit of time because it likely triggers some large zip file downloads)
[x] Run make all-up-yes (because we made a change in the rds-cluster module in addition to the changes in the cumulus module)
[x] Run smoke test
[x] If smoke test succeeds, open PR

NASA-IMPACT / csdap-cumulus

Cumulus upgrade to v16.1.1 #265