Angular 19 SSR/hybrid rendering engine: cross-request cache

### Command

run

### Description

It would be a useful optimization to cache some requests during SSR across requests to the SSR server. Some of the API requests have infrequently changing data. Pulling the response from cache would save a lot of network time, especially if the response is big.

Flow:
User 1 makes makes request to Angular SSR server -> SSR makes requests to API in order to gather data for rendering -> request gets cached -> user 1 receives an html response.
User 2 makes request to Angular SSR server -> SSR server would make API request in order to gather data, but instead pulls the response from the cache -> user 2 receives an html response.

One possible implementation would be to consider Cache-Control header and cache the response in the server for the time specified.

If this will not be considered - what would you say is the best approach in order to optimize these kind of API requests? Perhaps a wrapper around `global.fetch` in Node server (where Angular engine runs) which would monitor every API request and store in some local cache?

### Describe the solution you'd like

_No response_

### Describe alternatives you've considered

_No response_

Aucun fichier, test ou point d’entrée concret n’est nommé. Commencez par suivre le chemin de la requête Angular SSR/hybrid rendering dans le serveur Node et par examiner l’utilisation de global.fetch ; définissez la portée du cache, son expiration et le comportement de Cache-Control avant l’implémentation. Pour considérer le travail comme terminé, il faudrait un design convenu, une implémentation et une couverture du cache entre les requêtes.

Rédigé par le modèle d'indexation à partir du texte de l'issue.