Abort Cloud Code execution when server has timed out

Is your feature request related to a problem? Please describe.

Given a Parse Server is setup to have a request timeout set of 10s:

const httpServer = require('http').createServer(app);
httpServer.timeout = 10 * 1000;

When a Cloud Code function is called and takes 20s to execute, NodeJS destroys the socket after 10s, but the Cloud Code function keeps on executing. Some cloud code functions are just wasting resources in that case and it should be possible to abort them in a controlled manner.

Describe the solution you'd like

Add a status parameter to the request object of the Cloud Code function that is the current status of the request. When a request is aborted due to socket timeout, the status should be updated accordingly.

This allows it to query the request object at different points during the Cloud Code execution and abort the execution in a controlled manner without causing data inconsistencies.

The callback function of the server timeout can be used to update the request status:

httpServer.setTimeout(10 * 1000, {
   request.status = Parse.Cloud.FunctionRequest.Status.Timeout;  // pseudo code
});

Inside the Cloud Code function the status can be observed and processing aborted in a controlled manner:

Parse.Cloud.define("example", async (request) => {
   // Do something
   // ...

   if (request.status == Parse.Cloud.FunctionRequest.Status.Timeout) {
      // Abort here
      return;
   }

   // Do more
   // ...
});

Describe alternatives you've considered

Any ideas for alternatives?

Additional context

Originally posted as a question on SO, but since it seems that there is no current solution to this, opening an issue here.

No files or tests are named. Start by tracing the Parse.Cloud.define request lifecycle and the httpServer timeout callback described in the issue; done means a timed-out request exposes an updated status to Cloud Code so execution can detect it and stop in a controlled manner.