fix cron job metadata name lenght
When deploying to staging, this error appeared:
`one or more objects failed to apply, reason: CronJob.batch "staging-datasets-server-job-clean-duckdb-index-downloads" is invalid: metadata.name: Invalid value: "staging-datasets-server-job-clean-duckdb-index-downloads": must be no more than 52 characters,CronJob.batch "staging-datasets-server-job-clean-duckdb-index-job-runner" is invalid: metadata.name: Invalid value: "staging-datasets-server-job-clean-duckdb-index-job-runner": must be no more than 52 characters`

Reducing the job name to see if it fix the error
fix cron job metadata name lenght: When deploying to staging, this error appeared:
`one or more objects failed to apply, reason: CronJob.batch "staging-datasets-server-job-clean-duckdb-index-downloads" is invalid: metadata.name: Invalid value: "staging-datasets-server-job-clean-duckdb-index-downloads": must be no more than 52 characters,CronJob.batch "staging-datasets-server-job-clean-duckdb-index-job-runner" is invalid: metadata.name: Invalid value: "staging-datasets-server-job-clean-duckdb-index-job-runner": must be no more than 52 characters`

Reducing the job name to see if it fix the error