Re-enable software vitality

[bfabio]

Re-enable software vitality which was removed by #1484.

The API supports vitality in software resources, via the opaque vitality field:

vitality | string minLength: 1 maxLength: 99999 pattern: .* default: null example: 90,100,94,12
The vitality of the software repository, indicating health, activity, or metrics relevant to its condition. This is a opaque string, and users of the API can choose their own format. The Italian catalog, for example, uses comma-separated values for daily vitality scores (0-100) (see https://github.com/italia/publiccode-crawler/blob/main/vitality-ranges.yml).

As of now there are two crawlers cronjobs running:

❯ kubectl get cronjobs
NAME                          SCHEDULE    SUSPEND   ACTIVE   LAST SCHEDULE   AGE
publiccode-crawler            0 0 * * *   False     0        16h             545d
publiccode-crawler-with-api   0 0 * * *   False     0        16h             66d

The first one is the legacy branch, which can be decommissioned, but has storage because it clones the repo to calculate the vitality.
We should use the new crawler (the second one), with the first one's storage configuration.

So the steps are:

• Implement Use the API to save vitality publiccode-crawler#405
• Maybe implement Use a better method to incrementally save metadata for vitality publiccode-crawler#380 to use the less storage possible
• Add storage publiccode-crawler-with-api
• Remove publiccode-crawler
• Revert remove: temporarly remove vitality #1484 and adapt it to get vitality from the API