make akash-api a SDK

[troian]

NOTE This issue description will be updated within next few weeks

Refactor Akash-API layout

Restructure akash-api layout

Restructuring is being done within sdk-47 branch

• [x] migrate protobuf generation to use buf @troian
  • [x] split proto code-generation into language targets @troian
  • [x] proto-gen-go
  • [x] proto-gen-ts
  • [x] proto-gen-doc

• [x] migrate all proto files to Cosmos-SDK v0.47.x (at time of writing v0.47.11) @troian

  • [x] - split proto/akash/node/base in to
    • [x] attributes as v1
    • [x] resources as v1beta4
    • [ ] implement migrations @troian
  • [x] make proto/akash/node/audit as v1
    • [ ] implement migrations @troian
  • [x] - make proto/akash/node/cert as v1
    • [ ] implement migrations @troian
  • [x] - split proto/akash/node/deployment
    • [x] - types depending on resources as v1beta4
    • [x] - rest as v1
    • [ ] implement migrations @troian

  • [x] - split proto/akash/node/market

    • [x] - types depending on resources and deployment as v1beta5
    • [x] - rest as v1
    • [ ] implement migrations @troian
  • [x] - make proto/akash/node/escrow as v1
    • [ ] implement migrations @troian
  • [x] - make proto/akash/node/provider as v1beta4
    • [ ] implement migrations @troian
  • [x] - remove proto/akash/node/troian as cosmos-sdk v0.47.x has implemented min deposit for governance proposal.
  • [ ] implement migrations @troian

Golang

• [x] Create vanity domain for akash packages (akashd.io) @troian
• [x] rename go directory to sdk @troian
  • [x] set root vanity url to go.akashd.io/sdk @troian]
  • [x] migrate SDL from node to github.com/akash-network/akash-api/sdk/sdl
    • [ ] declare it as module go.akashd.io/sdk/sdl @troian
  • [ ] copy all tx/query commands from node and cosmos-sdk under cli dir. This will become reference implementation of the CLI @troian
• [ ] provide client examples @troian @chainzero

TS

• [ ] perform and test codegen @ygrishajev
• [ ] provide client examples @ygrishajev

[anilmurty]

Just a note that we have 3-4 customers using the API to integrate their platforms today (Solve Care, Brev, Prime-Intellect in production + a bunch that are planning to integrate). So we have to ensure the API changes are backward compatible or bump the major version and communicate to the customers and ensure they can migrate to the new version, before we release.