[Release] Embed tasks in the cli

[sciabarracom]

Why you need it?

it is required to do a release embeding the tasks in the cli

How it could be?

1. Change the looks logic of ops to locate the OPS_ROOT:
   Currently it looks for a folder called ./olaris then in ~/.ops/$OPS_BRANCH/olaris

We should add also add ~/.ops/.olaris as "last resort" - the .ops/.olaris will be initialized by the cli on first run using embedded task

2. change the build to clone apache/openservleress-task 0.1.0 and embed in the binary

3. at the cli startup, if there is not a ~/.ops./.olaris, extract it from the embedded
   tasks

Other related information

This way the cli will be able to work without downloading anything but you can still update the task with ops -update

[wtfzambo]

Feel free to assign this to me in the meantime.

[wtfzambo]

Cc. @sciabarracom , @d4rkstar

[ValerioJiang]

• Tasks are embedded from apache/openserverless-task version 0.1.0
• On first run, if tasks are missing, they are extracted into ~/.ops/.olaris
• The CLI can run offline on a clean machine
• Task lookup includes the new fallback ~/.ops/.olaris
• Existing behavior is preserved
• Documentation mentions the new behavior

[wtfzambo]

• Tasks are embedded from apache/openserverless-task version 0.1.0[ ] On first run, if tasks are missing, they are extracted into ~/.ops/.olaris[ ] The CLI can run offline on a clean machine[ ] Task lookup includes the new fallback ~/.ops/.olaris[ ] Existing behavior is preserved[ ] Documentation mentions the new behavior

as far as I tested in my PR, all points check out except the documentation, as I wasn't sure where to document these changes in specific. Cc. @sciabarracom , any preference?