Use new definitions from api-common

[Marenz]

fixes #242

WIP - not yet implemented in common

[Copilot]

Pull Request Overview

This PR updates dependency versions and migrates proto definitions to use the new api-common layout.

• Updated pyproject.toml to use a Git URL for frequenz-api-common and adjusted the protobuf version.
• Revised dispatch.proto to import and use definitions from the new electrical_components and types namespaces.

Reviewed Changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated no comments.

File	Description
pyproject.toml	Downgraded protobuf version and switched frequenz-api-common dependency to a Git URL.
proto/frequenz/api/dispatch/v1/dispatch.proto	Updated imports and type references to the new api-common definitions.

Files not reviewed (1)

• submodules/frequenz-api-common: Language not supported

[Marenz]

THis is to match the common api version

[llucax]

Oh, interesting. I wonder if there is a better way to do this, it kind of sucks to have such a strong interdependence...

[llucax]

On the other hand, if this is about the protobuf message about runtime and build version mismatch, using different point releases of the same minor should work. Are you sure this is really needed?

[llucax]

Are you sure you want to make the jump to an unrelated unreleased common API?

[Marenz]

what do you mean unrelated?
I think technically this is on protocol level a no-op, so it should be okay?

[llucax]

Sorry, typo, I meant unreleased.

[llucax]

I think technically this is on protocol level a no-op, so it should be okay?

No, sadly this also translate to Python dependencies.

[llucax]

Which means this code won't be usable with the SDK unless the microgrid API client also uses exactly the same git hash as dispatch.

[llucax]

If we want to keep the development so we don´t need to do a huge update after the api-common release, maybe we can do it in a feature branch, so we don't block the development of the "stable" branch