GIGAHOST: Add Gigahost DNS provider

[jochristian]

Overview

Adds a DNS Service Provider for Gigahost (a Norwegian host). This is a DnsProvider only — not a registrar.

Capabilities

• get-zones, preview, and push
• Diff strategy: diff2.ByRecord() (Gigahost assigns a per-record ID)
• Record types: A, AAAA, CNAME, MX, TXT, NS, plus ALIAS, CAA, DNAME, NAPTR, PTR, SRV
• GetNameservers returns Gigahost's fixed nameservers (ns1/ns2/ns3.gigahost.no)
• ListZones supported; zone creation is not (zones must exist in the Gigahost panel)

API notes handled

• All IDs arrive as JSON strings; record_priority/record_ttl may be quoted strings or null (handled by a tolerant unmarshaler).
• The records endpoint returns an apex SOA that is ignored on read.
• DELETE requires name+type+value query params: name+type alone removes the entire RRset, so value is needed to delete a single record when several share a name+type (round-robin A, multiple MX/TXT).
• CAA/SRV/NAPTR are stored as full RFC1035 presentation strings in record_value.
• Unsupported types (TLSA, SSHFP, HTTPS, SVCB, DS, LOC, …) are rejected by the API and left untouched if already present.

Testing

Verified end-to-end against a live zone: create → idempotency → change → idempotency → delete round-trips for every supported record type (including round-robin delete); the zone was restored to its original state afterward.

Config

{
  "gigahost": {
    "TYPE": "GIGAHOST",
    "apikey": "flux_live_your-api-key"
  }
}

Includes the provider docs page, SUMMARY.md entry, an integrationTest profile, and regenerated files via bin/generate-all.sh.

[TomOnTime]

Thank you for submitting this PR. I'll review it in the coming week.

In the meanwhile, let's set up credentials so that the provider can be added to our automated testing system. Instructions are here: https://docs.dnscontrol.org/developer-info/byo-secrets#donate-secrets-to-the-project

[jochristian]

Hi @TomOnTime, I will check whats possible to do for Gigahost regarding automatic testing.

[TomOnTime]

Please resolve the conflicts and I'll do another quick review. We should be able to get this into the next release. Thanks!

[jochristian]

Hi @TomOnTime, the conflict should have been resolved now.

[TomOnTime]

Thank you for contributing this new provider, @jochristian !

Three notes:

1. By now you should have received a Github invite to have the "triage" role for this repo. Please accept the invite so we can assign bugs to you.
2. @fm: Faisal Misle is our “liaison to maintainers”. Please send him an email from your preferred address to dnscontrol so we can stay in touch? His email address is f at faisal dot fm
3. Please consider setting up a test account for use by our automated testing. This will mean we can test the provider every release in an automated manner. Info is here: https://docs.dnscontrol.org/developer-info/byo-secrets#donate-secrets-to-the-project