Akamai provider replaces per domain nameservers with deprecated shared Authoritative name servers

[hallorans-nca]

Describe the bug
A eDNS zone that has 'per domain' nameservers will get those nameservers replaced with the old deprecated shared nameservers.

To Reproduce

1. In the Akamai portal, create a primary zone, add a test record set, and then activate the zone
2. Wait for the zone to be active
3. confirm the nameservers provided via dig match the list given in the portal
4. Create a change to the zone via dnscontrol
5. Preview the change, and see the nameservers are being updated along with the change above

For example, with a zone containing the following information:

D("zzztestdnscontrol.com.au", REG_NONE,
    DnsProvider(EDNS),
    NAMESERVER_TTL("1d")
)

dig zzztestdnscontrol.com.au @a3-65.akam.net ns +noall +answer +nocomments
zzztestdnscontrol.com.au. 86400 IN      NS      a1-205.akam.net.
zzztestdnscontrol.com.au. 86400 IN      NS      a11-64.akam.net.
zzztestdnscontrol.com.au. 86400 IN      NS      a20-65.akam.net.
zzztestdnscontrol.com.au. 86400 IN      NS      a28-65.akam.net.
zzztestdnscontrol.com.au. 86400 IN      NS      a3-65.akam.net.
zzztestdnscontrol.com.au. 86400 IN      NS      a26-67.akam.net.

This list of nameservers matches what is shown in the portal.

sops exec-file creds.live.json 'dnscontrol preview --creds {} --domains zzztestdnscontrol.com.au'
CONCURRENTLY checking for 0 zone(s)
SERIALLY checking for 1 zone(s)
Serially checking for zone: "zzztestdnscontrol.com.au"
******************** Domain: zzztestdnscontrol.com.au
1 correction (akamaiedgedns)
#1: Ensuring zone "zzztestdnscontrol.com.au" exists in "akamaiedgedns"
CONCURRENTLY gathering records of 0 zone(s)
SERIALLY gathering records of 1 zone(s)
Serially Gathering: "zzztestdnscontrol.com.au"
******************** Domain: zzztestdnscontrol.com.au
7 corrections (akamaiedgedns)
#1: - DELETE TXT createrecordset.zzztestdnscontrol.com.au "Test" ttl=1800
#2: ± MODIFY NS zzztestdnscontrol.com.au: (a1-205.akam.net. ttl=86400) -> (a1-246.akam.net. ttl=86400)
   ± MODIFY NS zzztestdnscontrol.com.au: (a11-64.akam.net. ttl=86400) -> (a12-67.akam.net. ttl=86400)
   ± MODIFY NS zzztestdnscontrol.com.au: (a20-65.akam.net. ttl=86400) -> (a13-64.akam.net. ttl=86400)
   ± MODIFY NS zzztestdnscontrol.com.au: (a26-67.akam.net. ttl=86400) -> (a18-65.akam.net. ttl=86400)
   ± MODIFY NS zzztestdnscontrol.com.au: (a28-65.akam.net. ttl=86400) -> (a5-66.akam.net. ttl=86400)
   ± MODIFY NS zzztestdnscontrol.com.au: (a3-65.akam.net. ttl=86400) -> (a8-67.akam.net. ttl=86400)
Done. 8 corrections.

As you can see from the preview, dnscontrol wants to replace all of the nameservers.
(The createrecorset.zzztestdnscontrol.com.au was the record I created in the Akamai portal to allow the zone to be activated)

Expected behavior
dnscontrol should not replace the per domain nameservers with the old shared name servers

DNS Provider

• Akamai

Additional context
This is using dnscontrol 4.36.1