Adapt network to the new config based HTTP API (backend)

[teclator]

Problem

There is a new config based HTTP API and all the services needs to be adapted. The aim of this PR is to adapt the network backend service (replace #2840).

• feat: add a new config-based API #2715

Solution

In the new architecture all the Agama modules will live in its own package implementing the actors/service as described in (#2715), but as network was already using a actors model using an enums approach it was decided to use the current service in the first iteration of changes.

Changes done

• Added the actions for getting the system, proposal and current network configuration using the actual actions passing messages system based on enums.
• All the structs or types that are related to the API (needs to be serialized) has been moved to agama-utils, it was decided to not depend on agama-lib anymore. The types will be re-exported to be used by agama-network when needed.
• As the current merge is concatenating the connections array, the patch (updateConfig) will replace the connections with the given one when present, but is something we need to revisit and decide how to do it in a better way.
• Removed the network web service.
• As the proposal, system info and config contains similar collections and just change the absence or presence of some of them we have introduced the NetworkCollection and NetworkConnectionCollections in order to do the conversion between them.

TODO

• Move to the actors/service model using traits instead of enums and adding the issues and progress monitor to the network service.
• Remove all the actions which are not needed anymore (old network web service).
• Add unit tests covering the new approach.

[coveralls]

coverage: 64.118% (-0.7%) from 64.776%
when pulling f5f25e7 on agama-api-v2_network-backend
into da86580 on api-v2.

[imobachgs]

I wonder if it would be better to return a Result instead.