Cron timeout doesn't work

### Version Information

Server Version: v2.27.0
CLI Version (for CLI related issue):

### Environment

Not Cloud

### What is the current behaviour?

I receive an "upstream request timeout" to an API endpoint that takes approximately 50 seconds to complete. The request did not abort and indeed completed on the other end.

### What is the expected behaviour?

I expect to see the actual response of the server and not an "upstream request timeout".

### How to reproduce the issue?

1. Create a Cron Trigger to some external service
2. Ensure that external service delays its response 60 seconds
3. Set the Cron Trigger timeout to 120 seconds under Advanced Settings->timeout in seconds
4. Wait
5. See the big red X status on the invocation log and the "upstream request timeout" when expending the details

### Screenshots or Screencast

Don't think that would help here.

### Please provide any traces or logs that could help here.

Regrettably these are not supplied by Hasura; not even the end time of the invocation is logged.

### Any possible solutions/workarounds you're aware of?

No

### Keywords

hasura cron upstream request timeout

Start with the Cron Trigger flow described in the reproduction steps and verify how the Advanced Settings timeout is applied to an external service response. Reproduce the 60-second delay with a 120-second timeout, then confirm the invocation log shows the actual response rather than an upstream request timeout.

Written by the indexing model from the issue text.