Updating old Contact info

Hey Folks, what are your thoughts on maintaining contact info via actual terraform ?

Something like this...

https://github.com/KingBain/cds-dns/tree/contact-info?tab=readme-ov-file#examples

```hcl
locals {
record_metadata_rescheduler_cds_snc_ca_CNAME = {
owner = "alpha-omega@cds-snc.ca"
purpose = "Cname for domain for record scheduler"
}
}

resource "aws_route53_record" "rescheduler-cds-snc-ca-CNAME" {
zone_id = aws_route53_zone.cds-snc-ca-public.zone_id
name = "rescheduler.cds-snc.ca"
type = "CNAME"
records = [
"d31g0redbbnj2z.cloudfront.net"
]
ttl = "300"

}
```

The biggest issue for me is I have moved away from supporting sp.ssc.alpha.canada.ca domain, but alot of the history is still pointing back at me. #249

I dont see away to point it to someone else.

I figure doing it as a local TF variable would make it parseable with a tf plan or other generic tf parser

@CalvinRodo @gcharest @patheard

Start by reviewing the proposed cds-dns contact-info example and issue #249, then inspect the repository's existing DNS configuration. Clarify whether contact metadata should be represented as Terraform locals and how ownership changes should be handled; the work is done when the maintainers agree on an implementable approach.

Written by the indexing model from the issue text.