chore: add pre-prod

Author: acanbym

docs/technical-standards/Reference/hosting-standards/tagging.md

@@ -12,7 +12,7 @@ To ensure we can consistently search for, and report on, the tags we use, you sh
 
 - `Application`: The full name of the application or service. This should match the name used in the Service Catalogue, e.g.  `Repairs Hub`, `Common Fate`.
 - `TeamEmail`: The email address of the team responsible for the operation of the service. Must be a valid email group, not an individual.
-- `Environment`: The name of the environment, must be one of `dev`, `stg`, `prod` or `mgmt`[^environment-tags-source].
+- `Environment`: The name of the environment, must be one of `dev`, `stg`, `prod`, `pre-prod` or `mgmt`[^environment-tags-source].
 
 ### Mandatory tags for data-holding resources
 
@@ -28,7 +28,7 @@ You will not be able to deploy the above resources if they are not tagged with t
 ### Optional tags
 
 - `AutomationBuildUrl`: URL of the automation build, must be a valid URL.
-- `BackupPolicy`: The backup policy to apply to the resource. If present must be one of `Dev`, `Stg`, `Preprod`, `Prod`, `Mgmt`.
+- `BackupPolicy`: The backup policy to apply to the resource. If present must be one of `Dev`, `Stg`, `Prod`.
 - `Confidentiality`: Data confidentiality of the infrastructure. Only mandatory for infrastructure which holds data, e.g. EC2, RDS, EBS, DynamoDB, Glue, and S3. Optional for all other infrastructure. Must be one of `Internal`, `Restricted`, or `Public`[^confidentiality-tags-source].
 - `Department`: The service area this system serves.
 - `WeekendShutdown`: If present, regardless of the value provided the resource will be shut down over the weekend.