EREGCSC-2906 Mitigate IP address issue

[cgodwin1]

Resolves #2906

Description-

Early in 2024 we were receiving experimental deploy failures due to one of our subnets being out of available IPv4 addresses. To mitigate this, we removed the text extractor from the VPC. The eCFR/FR parsers were already not in the VPC, so this permanently resolved the issue when deploying with Serverless.

Recently with the transition work to CDK, we started receiving this error again because all experimental deploy lambda functions were being assigned to the VPC. This PR fixes that.

This pull request changes...

• Text extractor + FR parser + eCFR parser lambdas removed from the VPC

Steps to manually verify this change...

1. Confirm all green check marks (for the first time in a while!) This means all lambdas are deploying properly.
2. If better validation is desired, log into the VPN and go to the dev AWS account.
3. Go to the VPC dashboard, then on the left sidebar click "Subnets".
4. For each of the private subnets on that page, copy the "Subnet ID" field to your clipboard.
5. Run the following AWS CLI command: aws ec2 describe-network-interfaces --filters Name=subnet-id,Values=<SUBNET ID HERE> | grep Description | grep 1518 (replace <SUBNET ID HERE> with your subnet ID, for example subnet-123abc).
6. You should see an empty response for each subnet. This confirms that no resources related to this pull request are associated with any of eRegs' private subnets.

[github-actions]

✨ See the Django Site [in action][1] ✨

[1]:

[github-actions]

✨ See the Django Site [in action][1] ✨

[1]:

[PhilR8]

25 green check marks! LGTM!