TF crash akamai_dns_record with bad data

gistfile1.txt

│ Error: Request cancelled
│ 
│ The plugin6.(*GRPCProvider).UpgradeResourceState request was cancelled.
╵

Stack trace from the terraform-provider-akamai_v6.0.0 plugin:

panic: runtime error: slice bounds out of range [:4] with capacity 0

goroutine 144 [running]:
github.com/akamai/terraform-provider-akamai/v6/pkg/providers/dns.FullIPv6({0x0, 0x0, 0xc0150e84c0?})
        github.com/akamai/terraform-provider-akamai/v6/pkg/providers/dns/resource_akamai_dns_record.go:1380 +0x2d3
github.com/akamai/terraform-provider-akamai/v6/pkg/providers/dns.diffQuotedDNSRecord({0xc017355b10, 0x1, 0x1}, {0xc017355b20, 0x1, 0x1}, {0xc0150e84a0, 0x19}, {0xc0150e84c0, 0x19}, ...)
        github.com/akamai/terraform-provider-akamai/v6/pkg/providers/dns/resource_akamai_dns_record.go:505 +0xd76
github.com/akamai/terraform-provider-akamai/v6/pkg/providers/dns.dnsRecordTargetSuppress({0xc014bdc310, 0x8}, {0xc0150e84a0, 0x19}, {0xc0150e84c0, 0x19}, 0xc015c6e3c0?)
        github.com/akamai/terraform-provider-akamai/v6/pkg/providers/dns/resource_akamai_dns_record.go:466 +0x9a5
github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.schemaMap.diff(0x6?, {0x1e67cd0, 0xc015167e60}, {0x1b3e643, 0x6}, 0xc015c6e3c0, 0xc0147fc580, {0x1e6c610?, 0xc0147fc800}, 0x0)
        github.com/hashicorp/terraform-plugin-sdk/v2@v2.27.0/helper/schema/schema.go:1143 +0x392
github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.schemaMap.Diff(0xc015c4cae0, {0x1e67cd0, 0xc015167e60}, 0xc014517380, 0xc0152b7710, 0x0, {0x19e2be0, 0xc0144e26f0}, 0x0)
        github.com/hashicorp/terraform-plugin-sdk/v2@v2.27.0/helper/schema/schema.go:678 +0x332
github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.(*Resource).SimpleDiff(0x1e68050?, {0x1e67cd0?, 0xc015167e60?}, 0xc014517380, 0x199d020?, {0x19e2be0?, 0xc0144e26f0?})
        github.com/hashicorp/terraform-plugin-sdk/v2@v2.27.0/helper/schema/resource.go:917 +0xd5
github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.(*GRPCProviderServer).PlanResourceChange(0xc015ad1ed8, {0x1e67cd0?, 0xc015167b60?}, 0xc01596c8c0)
        github.com/hashicorp/terraform-plugin-sdk/v2@v2.27.0/helper/schema/grpc_provider.go:744 +0x976
github.com/hashicorp/terraform-plugin-mux/tf5to6server.v5tov6Server.PlanResourceChange({{0x1e71c40?, 0xc015ad1ed8?}}, {0x1e67cd0, 0xc015167b60}, 0x0?)
        github.com/hashicorp/terraform-plugin-mux@v0.11.2/tf5to6server/tf5to6server.go:81 +0x54
github.com/hashicorp/terraform-plugin-mux/tf6muxserver.muxServer.PlanResourceChange({0xc016dca4e0, 0xc018b107f0, 0xc016dca510, 0xc016dca540, {0xc016a73220, 0x2, 0x2}}, {0x1e67cd0?, 0xc0151676b0?}, 0xc01596c870)
        github.com/hashicorp/terraform-plugin-mux@v0.11.2/tf6muxserver/mux_server_PlanResourceChange.go:66 +0x22f
github.com/hashicorp/terraform-plugin-go/tfprotov6/tf6server.(*server).PlanResourceChange(0xc00011ef00, {0x1e67cd0?, 0xc015166ae0?}, 0xc0002ecaf0)
        github.com/hashicorp/terraform-plugin-go@v0.18.0/tfprotov6/tf6server/server.go:784 +0x56b
github.com/hashicorp/terraform-plugin-go/tfprotov6/internal/tfplugin6._Provider_PlanResourceChange_Handler({0x1ae3980?, 0xc00011ef00}, {0x1e67cd0, 0xc015166ae0}, 0xc0002ec9a0, 0x0)
        github.com/hashicorp/terraform-plugin-go@v0.18.0/tfprotov6/internal/tfplugin6/tfplugin6_grpc.pb.go:404 +0x169
google.golang.org/grpc.(*Server).processUnaryRPC(0xc0147ccb40, {0x1e70330, 0xc016f0e1a0}, 0xc01731cc60, 0xc016e80360, 0x2776608, 0x0)
        google.golang.org/grpc@v1.56.3/server.go:1335 +0xde7
google.golang.org/grpc.(*Server).handleStream(0xc0147ccb40, {0x1e70330, 0xc016f0e1a0}, 0xc01731cc60, 0x0)
        google.golang.org/grpc@v1.56.3/server.go:1712 +0x9e7
google.golang.org/grpc.(*Server).serveStreams.func1.1()
        google.golang.org/grpc@v1.56.3/server.go:947 +0xbb
created by google.golang.org/grpc.(*Server).serveStreams.func1 in goroutine 38
        google.golang.org/grpc@v1.56.3/server.go:958 +0x145

Error: The terraform-provider-akamai_v6.0.0 plugin crashed!

This is always indicative of a bug within the plugin. It would be immensely
helpful if you could report the crash with the plugin's maintainers so that it
can be fixed. The output above should help diagnose the issue.