feat(dist)!: make blueprint an IPLD, use CID as module ids [NET-412 NET-432]

[justprosh]

Previously, the blueprint looked like this:

{
  "name": "trust-graph",
  "dependencies": [ "hash:someblake3hash", "name:trust-graph" ]
}

Module IDs were represented as blake3 hashes. Modules could also be specified by names, which were local to each peer and could be easily overwritten. The blueprint ID was a blake3 hash of the dependencies.

In deals, we already use CIDs for modules and worker definitions, which can be seen as a combination of service blueprints and spell definitions.

This PR contains the next BREAKING CHANGES:

• Module IDs are now CIDs of the module wasm.
• Blueprints have been converted to IPLD structures.
• Blueprint IDs are now CIDs of the IPLD structure.
• dist.make_blueprint returns a string representing the blueprint in IPLD format, which can be directly added to IPFS using ipfs dag put. This ensures the same CID is used everywhere.
  The updated blueprint now looks like this:

Blueprint now looks like this:

{
  "name": "trust-graph",
  "dependencies": [
    {
      "/": "bafybeieh62qys3ln2qiqbye2jgynxkfzzlvebw7dtpsqgv45p6qw62hk7u"
    },
    {
      "/": "bafybeigrqdxshsoxwp27s47tr3inn6pkt3ggh7hzwcqz7qgfrxmw3j77vu"
    }
  ]
}

The strings bafybeieh62qys3ln2qiqbye2jgynxkfzzlvebw7dtpsqgv45p6qw62hk7u and bafybeigrqdxshsoxwp27s47tr3inn6pkt3ggh7hzwcqz7qgfrxmw3j77vu are the CIDs of the respective modules.

[linear]

NET-432 CID[IPLD]-fication of blueprints

NET-412 Use CIDs for blueprint ids

Right now it is some blake-something hash and it is impossible to compare CID to blueprint id

[kmd-fl]

Does it mean that aqua deploy_service/fluence workers deploy will stop working properly?