Consider adding more cache header options to DiscoveryOptions

[RolandGuijt]

Please see DuendeSoftware/Support#1399

[josephdecock]

ASP.NET Core has lots of built in caching support that has been improving over the past few releases. There's now both ResponseCaching (http header based) and OutputCaching (new in .net 7, controlled purely server side).

Anders brought up that we might benefit from using the built in endpoint infrastructure for better observability (#1575 (comment)). I think we could get some benefit from the framework's caching implementations as well.

Of course, that's a major change with big implications. We could always just add more options. There's about a dozen cache control directives possible (https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cache-Control#cache_directives). Which ones would we support? Should we try to respect request headers, as the framework's Response Cache does?