[ON HOLD][13.0] Add job_auto_delay decorator

[guewen]

This is a new decorator, to use instead of @job on methods,
that transforms a method to a method automatically delayed as job when
called.

A typical use case is when a method in a module we don't control is called
synchronously in the middle of another method, and we'd like all the calls
to this method become asynchronous.

Closes #238

[lmignon]

LGTM and good idea! (Code review)

[jgrandguillaume]

This is so elegant 👍

[simahawk]

LG, just small glitches.
BTW what about #255 ?

[guewen]

@simahawk I fixed the small glitches and force-pushed directly

[etobella]

Great idea @guewen this is something I always needed and had to solve using context keys. This is much more cleaner 😄

[guewen]

Do not merge yet, I'm investigating an error:

AttributeError: method cron_actions on stock.buffer(5577,) is not allowed to be delayed, it should be decorated with odoo.addons.queue_job.job.job

And I suspect it happens when other modules redefine the same method. To be continued...

[guewen]

And I suspect it happens when other modules redefine the same method.

I confirm this. I hope I can find a way to prevent this.

[guewen]

AttributeError: method cron_actions on stock.buffer(5577,) is not allowed to be delayed, it should be decorated with odoo.addons.queue_job.job.job

This is not an issue only with @job_auto_delay, we have the error with @job.
If I have such dependencies:

module_a
  |- module_b
  |- module_c

module_b and module_c have no dependencies on each other.

In module_a, we have a method StockMove._update_foo.
In module_b, we add @job on StockMove._update_foo.
In module_c, we have another override of StockMove._update_foo, without decorator.

It seems that depending on the loading order, we'll lose the properties added by @job.

[guewen]

I proposed #275 that works by patching the method instead of using a decorator.
It needs #274 that I still have to finalize.