REFACTOR Make queue_job dependencies optional

[ecino]

• NEW module queue_job_sh_safe that will safely use queue_jobs when available and fallback to an alternate mechanism with ir_cron in case the module is not installed.
• This is useful for Nordic using odoo.sh on which queue jobs are prohibited and not optimal for the infrastructure

[greptile-apps]

Confidence Score: 3/5

The fallback queue path still needs attention around replacement jobs that receive follow-up work while already running.

• The core optional-queue fallback can enqueue and execute a simple job through the replacement cron path.
• The identity-key merge behavior can lose work when a running replacement job receives additional record ids after cron has already materialized its recordset.
• The changes touch many asynchronous call sites, so correctness depends on the replacement queue preserving delivery semantics under concurrent or repeated scheduling.

queue_job_optional/models/queue_job_replacement.py

T-Rex Logs

What T-Rex did

• Reviewed the initial environment state, noting that HEAD^ lacks queue_job_optional/models/base.py and that importing Odoo is not possible.
• After enqueue, the log shows the queue job availability as False, one replacement was created, cron was triggered, and the replacement moved from pending to done with the job_result executed:[11]:alpha:42.
• After cron, the cron-run path was executed and showed the system moving from pending/None to done/executed-by-cron:[11]:alpha:42.

_{Ran code and verified through T-Rex}

_{Reviews (15): Last reviewed commit: "REFACTOR Make queue_job dependencies opt..." | Re-trigger Greptile}

[greptile-apps]

Processing Jobs Swallow Follow-Ups

When a second job with the same identity_key is queued while the first one is already processing, this branch merges the new res_ids into the row that cron is currently executing and returns it instead of creating pending work. The running cron already browsed the old ids and then marks the row done, so the newly merged ids are never executed for stable-key callers such as communication automation.