feat: add worker.create and worker.get_peer_id

[justprosh]

• scope.get_peer_id is removed
• worker.create accepts optional deal_id argument
  • if deal_id is omitted, init_peer_id is used to generate worker
• spell.install execution on host peer id implicitly call worker.create without deal_id arg
• worker.create returns error if worker for deal_id exists
• worker.get_peer_id accepts optional deal_id argument, return worker_id or throws an error

New worker flow for deals:

worker_id <- Worker.create(deal_id)
on worker_id:
     Spell.install(....)
     Spell.remove(...)
     Spell.update_trigger_config
     ...

[kmd-fl]

Shouldn't the manager of the peer be able to remove the spell?

[justprosh]

I think you're right