Revert "Add wiki.java.no alias"

[Asamsig]

Reverts #125

[github-actions]

Terraform Plan

🚧 Changes detected — Plan: 0 to add, 0 to change, 1 to destroy.

Plan output

Acquiring state lock. This may take a few moments...

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  - destroy

Terraform will perform the following actions:

  # module.dns.aws_route53_record.java_no_wiki will be destroyed
  # (because aws_route53_record.java_no_wiki is not in configuration)
  - resource "aws_route53_record" "java_no_wiki" {
      - fqdn                             = "wiki.java.no" -> null
      - id                               = "Z03374203CV7NEL5TVDXW_wiki.java.no_CNAME" -> null
      - multivalue_answer_routing_policy = false -> null
      - name                             = "wiki.java.no" -> null
      - records                          = [
          - "javabin.atlassian.net",
        ] -> null
      - ttl                              = 3600 -> null
      - type                             = "CNAME" -> null
      - zone_id                          = "Z03374203CV7NEL5TVDXW" -> null
    }

Plan: 0 to add, 0 to change, 1 to destroy.

─────────────────────────────────────────────────────────────────────────────

Saved the plan to: tfplan

To perform exactly these actions, run the following command to apply:
    terraform apply "tfplan"

---

LLM Review

Risk: 🟢 LOW

Plan removes a DNS CNAME record for wiki.java.no pointing to Jira, a routine cleanup operation with no security or cost implications.

• ✅ [routine] Removing DNS CNAME record wiki.java.no → javabin.atlassian.net. This is a standard DNS cleanup operation with no impact on active infrastructure.
• ✅ [routine] No resources are being created or modified, only one DNS record is being removed from configuration management.
• ✅ [routine] No security groups, IAM policies, or access controls are affected by this change.
• 💰 [cost] No cost implications - removing a Route53 DNS record has negligible impact on billing.
• ✅ [routine] All Lambda functions, monitoring, networking, and identity infrastructure remain unchanged. This is an isolated DNS record removal.