feat: Conduit Manifest

[kon14]

This PR introduces support for Conduit module declaration manifest objects as part of package.json.
Said manifest objects currently provide the following information:

• module version
• module dependencies

We should probably include support for detailing:

• a module's supported features
• feature dependencies
• dependencies on features
• migration state

Modules attempting to register themselves with Conduit provide their manifest file along with the registration request.
They are initially marked as pending, until their dependencies are met, at which point they receive a standardized activation gRPC request (activateModule()), allowing them to be properly brought up etc.

Also fixes grpc-sdk's isModuleUp().

BREAKING CHANGE:

Modified Conduit Config Service RPCs:
-Dropped ModuleExists()
-Dropped ModuleList()
-Refactored WatchModules() into WatchDeploymentState()
-Updated RegisterModule()

Services need also expose an ActivateModule() RPC
GetModules route return type modified.

I'm opening this up for review.
Requires further testing!

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update
• Refactor
• Build-related changes
• Other (please describe)

Does this PR introduce a breaking change?

• Yes
• No

The PR fulfills these requirements:

• It's submitted to the main branch
• When resolving a specific issue, it's referenced in the PR's description (e.g. fix #xxx, where "xxx" is the issue number)

[kon14]

Updated this, moving standardized Conduit module RPCs into a separate service.
I'll update the client getters to support dynamic modules (so that eg Core can setConfig() out-of-tree modules).