feat: 🎸 add indexes, based on recommendations from mongo cloud

[severo]

No description provided.

[codecov-commenter]

Codecov Report

Base: 90.14% // Head: 90.14% // No change to project coverage 👍

Coverage data is based on head (22b7624) compared to base (7cc7367).
Patch has no changes to coverable lines.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #728   +/-   ##
=======================================
  Coverage   90.14%   90.14%           
=======================================
  Files          99       99           
  Lines        5051     5051           
=======================================
  Hits         4553     4553           
  Misses        498      498           

Flag	Coverage Δ
jobs_mongodb_migration	83.46% <ø> (ø)
libs_libcommon	91.40% <ø> (ø)
services_admin	87.12% <ø> (ø)
services_api	90.13% <ø> (ø)
workers_datasets_based	92.01% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
libs/libcommon/src/libcommon/queue.py	96.10% <ø> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

[lhoestq]

Cool ! This way we can follow more easily the jobs per dataset ?

[severo]

Hmmm, no, it was required for a query when we look for the next job in the queue. I had added the priority field, but the index was not right.
Our cloud mongo db provides some recommendations about the indexes that could be created, based on the past queries. I just used that.

[severo]