Mitigate 429 errors in cloud function execution for validation reports

[cka-y]

Describe the Problem

While testing changes related to issue #826, I observed that running multiple validation reports simultaneously can result in 429 Too Many Requests errors. This happens when no additional instances of the Cloud Function responsible for updating the database are available. An example can be seen in this execution log: Cloud Console Execution Summary

Proposed Solution

To prevent these errors and improve reliability, consider one of the following solutions:

1. Cloud Task Implementation:
   Replace the direct function call in the workflow with a Cloud Task. Cloud Tasks provide automatic retries in case instances are unavailable, reducing the likelihood of 429 errors.

2. Pub/Sub Triggered Function:
   Transition the database update function from an HTTP-triggered function to a Pub/Sub-triggered function. This would decouple the function execution and ensure scalability during high workloads.

By implementing one of these solutions, the system can handle high concurrent requests more gracefully without impacting database updates.