caddy-frontend: increase proxy.config.http.negative_revalidating_lifetime.

In reality, proxy.config.http.cache.max_stale_age was used for stale cache lifetime in current ATS implementation.
Thus we increase proxy.config.http.negative_revalidating_lifetime value to the same value as proxy.config.http.cache.max_stale_age whose default is 604800.

software/caddy-frontend/buildout.hash.cfg

@@ -62,7 +62,7 @@ md5sum = 975177dedf677d24e14cede5d13187ce
 
 [template-trafficserver-records-config]
 _update_hash_filename_ = templates/trafficserver/records.config.jinja2
-md5sum = a6a6e21036f8c56e69ad7ac8a1dfd656
+md5sum = c79eb8e74b9bc097b4b3e48655fa1a1a
 
 [template-trafficserver-storage-config]
 _update_hash_filename_ = templates/trafficserver/storage.config.jinja2

software/caddy-frontend/templates/trafficserver/records.config.jinja2

@@ -25,7 +25,7 @@ CONFIG proxy.config.http.cache.open_write_fail_action INT 2
 CONFIG proxy.config.body_factory.template_sets_dir STRING  {{ ats_configuration['templates-dir'] }}
 # Support stale-if-error by returning cached content on backend 5xx or unavailability
 CONFIG proxy.config.http.negative_revalidating_enabled INT 1
-CONFIG proxy.config.http.negative_revalidating_lifetime INT 86400
+CONFIG proxy.config.http.negative_revalidating_lifetime INT 604800
 
 ##############################################################################
 # Thread configurations. Docs: