fix(response-cache): respect subgraph cache control TTL value

[ardatan]

Blocked by n1ru4l/envelop#2392
Fixes graphql-hive/gateway#542

When a subgraph returns cache control headers with a certain TTL, respect that during the calculation of overall TTL in the response cache plugin.

So this removes the extra configuration in the test, TTL is inherited from the subgraph response automatically.

For example, if there is a subgraph using Apollo Server that defines the default TTL without any @cacheControl directives. It prevents the response cache plugin to set the TTL infinite(which is the default of the response-cache plugin)

[github-actions]

Apollo Federation Subgraph Compatibility Results

Federation 1 Support	Federation 2 Support
_service 🟢 @key (single) 🟢 @key (multi) 🟢 @key (composite) 🟢 repeatable @key 🟢 @requires 🟢 @provides 🟢 federated tracing 🟢	@link 🟢 @shareable 🟢 @tag 🟢 @override 🟢 @inaccessible 🟢 @composeDirective 🟢 @interfaceObject 🟢

Learn more:

• Apollo Federation Subgraph Specification
• Compatibility Tests

[github-actions]

🚀 Snapshot Release (alpha)

The latest changes of this PR are available as alpha on npm (based on the declared changesets):

Package	Version	Info
@graphql-mesh/plugin-response-cache	0.103.13-alpha-20250129133641-c2ad468bab5a1293a6fbcc61acfd9c4ba0ae3d7b	npm ↗︎ unpkg ↗︎

[github-actions]

💻 Website Preview

The latest changes are available as preview in: https://d24228eb.graphql-mesh.pages.dev