DefaultDnsCache: apply MAX_SUPPORTED_TTL_SECS cap for `negativeTt…

…l` (#13637)

Motivation:

`DefaultDnsCache` already applies `MAX_SUPPORTED_TTL_SECS` as a cap for
`minTtl`/`maxTtl`, but does not apply it for `negativeTtl` that may
suffer from the same problem of scheduling tasks with too big delay on
the `EventLoop`. See

b47fb81

Modifications:

- Apply `MAX_SUPPORTED_TTL_SECS` cap for `negativeTtl` in ctor;

Result:

`negativeTtl` is capped by `MAX_SUPPORTED_TTL_SECS`.

resolver-dns/src/main/java/io/netty/resolver/dns/DefaultDnsCache.java

@@ -84,7 +84,7 @@ public DefaultDnsCache(int minTtl, int maxTtl, int negativeTtl) {
             throw new IllegalArgumentException(
                     "minTtl: " + minTtl + ", maxTtl: " + maxTtl + " (expected: 0 <= minTtl <= maxTtl)");
         }
-        this.negativeTtl = checkPositiveOrZero(negativeTtl, "negativeTtl");
+        this.negativeTtl = Math.min(Cache.MAX_SUPPORTED_TTL_SECS, checkPositiveOrZero(negativeTtl, "negativeTtl"));
     }
 
     /**