load latest offliner definition version

[elfkuzco]

Changes

• load offliner versions
• fetch the latest offliner definition from the versions array. Rationale is that API sorts versions in descending order which they were created and the most recent should be the latest. Could be violated by updating the wrong version but it's the only way of knowing which version is the "latest" as of now.

This closes #167

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 57.11%. Comparing base (c5a8882) to head (e276db7).

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #176      +/-   ##
==========================================
+ Coverage   56.95%   57.11%   +0.15%     
==========================================
  Files          12       12              
  Lines         546      548       +2     
  Branches       79       79              
==========================================
+ Hits          311      313       +2     
  Misses        233      233              
  Partials        2        2              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[elfkuzco]

This should not be merged until openzim/zimfarm#1422 is merged upstream

[benoit74]

zimit-frontend should not try to guess offliner definition to use, sorry for not having clear enough on that point.

It should have:

• an env variable (e.g. ZIMIT_DEFINITION_VERSION) which specifies the exact version to use
• a fallback if this env variable is not set to use the 'tag' from ZIMIT_IMAGE env variable
• since this is defined in the backend, I suggest we add a new endpoint to retrieve the offliner definition instead of letting the UI directly call the Zimfarm ; the fact that UI directly called the Zimfarm has anyway never been such a great idea since it means double configuration needed anytime we move the Zimfarm, while the UI should not care about that, only backend should ; this will allow to cleanup as well the UI code which will not need anymore the zimfarm_api configuration

[elfkuzco]

closing this as it's cleaner to implement in #177