[IT-4055] Remove CI deployment for dev environment

Once this is merged we will merge to git stage and prod
branches then manually tear down the openchallenges
dev stack and remove the git dev branch.

depends on Sage-Bionetworks-IT/organizations-infra#1329

README.md

@@ -314,11 +314,9 @@ OpenChallenges app.
 
 The workflow for continuous integration:
 
-* Create PR from the git dev branch
+* Create PR from the git stage branch
 * PR is reviewed and approved
 * PR is merged
-* CI deploys changes to the dev environment (dev.openchallenges.io) in the org-sagebase-openchallenges-dev account.
-* Changes are promoted (or merged) to the git stage branch.
 * CI deploys changes to the staging environment (stage.openchallenges.io) in the org-sagebase-openchallenges-prod account.
 * Changes are promoted (or merged) to the git prod branch.
 * CI deploys changes to the prod environment (prod.openchallenges.io) in the org-sagebase-openchallenges-prod account.

cdk.json

@@ -63,11 +63,6 @@
     "@aws-cdk/aws-codepipeline:defaultPipelineTypeToV2": true,
     "@aws-cdk/aws-kms:reduceCrossAccountRegionPolicyScope": true,
     "@aws-cdk/aws-eks:nodegroupNameAttribute": true,
-    "dev": {
-        "VPC_CIDR": "10.255.92.0/24",
-        "FQDN": "dev.openchallenges.io",
-        "CERTIFICATE_ARN": "arn:aws:acm:us-east-1:221082174873:certificate/4bd9e6ac-0951-485e-a132-e842aaf2ec58"
-      },
     "stage": {
         "VPC_CIDR": "10.255.93.0/24",
         "FQDN": "stage.openchallenges.io",