Endpoint to trigger statistic collector for a tenant

Description

The statistics collector will run twice a day for every provisioned tenant, but an user tenant will also be able to trigger the statistics collector for its tenant.

Each tenant can trigger this endpoint every 15 minutes. If some tenant trigger faster than that we can return 429.

If there is already a collector running for this tenant or for all tenants, return 409 and the message explaining.

In the GET statistics endpoint developed in the card above, we should also return the collector status for this tenant. If there are a collector running in this moment we can return: "RUNNING", if there is no collector running we can return “DONE", and if there was an error last collect, we can ignore and return the status “DONE" as well, since the statistics the user is going to see is related to the success.

In other words, we should bring the last statistics DONE, and also bring the last statistics status for this tenant.

Do not return other status like “Published" for example, because it’s a internal control. The consumers just want to know RUNNING or DONE.

If “PUBLISHED", "RUNNING" return "RUNNING”

If “ERROR", “CANCELED", “DONE", return “DONE"

But remember, the statistics should always be from the last "DONE" process