feat(worker_pool)!: Shift service creation to the worker pool [Fixes NET-716]

[gurinderu]

Description

This pull request contains the shifting of the service creation to the worker pool. Also, it has a separation of ParticleAppServices into the root & worker contexts.

Motivation

• shifting motivation: we want to isolate each service creation per worker
• context separation: we want to separate root & worker logic

Related Issue(s)

NET-716

Proposed Changes

Introduced PeerScope enum describes the current execution scope
ParticleAppServices - have separate structures for the root scope & worker scopes.
Workers can use a WorkerId only, doesn't work for the root worker.
PeerScope used everywhere instead of worker_id.

Screenshots (if applicable)

[Add any relevant screenshots or animated GIFs to showcase the changes.]

Checklist

• The code follows the project's coding conventions and style guidelines.
• All tests related to the changes have passed successfully.
• Documentation has been updated to reflect the changes (if applicable).
• All new and existing unit tests have passed.
• I have self-reviewed my code and ensured its quality.
• I have added/updated necessary comments to aid understanding.

Reviewer Checklist

• Code has been reviewed for quality and adherence to guidelines.
• Tests have been reviewed and are sufficient to validate the changes.
• Documentation has been reviewed and is up to date.
• Any questions or concerns have been addressed.

[linear]

NET-716 Shift service creation to the worker pool

[gurinderu]

I haven't finished reading the PR, but so far, I find that I don't like the PeerScope structure at all.

why?