removes RPC and make use of HTTP API

[brunocalza]

This PR removes the RPC protocol in favor of the HTTP API.

Lots of code removal, but in essence most of the code is the implementation of an HTTP client that follows this interface

type BasinProvider interface {
	CreateVault(context.Context, CreateVaultParams) error
	ListVaults(context.Context, ListVaultsParams) ([]Vault, error)
	ListVaultEvents(context.Context, ListVaultEventsParams) ([]EventInfo, error)
	WriteVaultEvent(context.Context, WriteVaultEventParams) error
}

Each one of the commands, calls a method.

Note: This PR changes some of the names in the code to be aligned with new terminology, but not all (you can expect for name refactoring in the next PRs). Also, the commands are still the same. In a future PR, I'll rename them.

[sanderpick]

Have we now killed the "namespace.relation" semantics?

[avichalp]

interesting that we still use the dot notation in the name: https://github.com/tablelandnetwork/basin-cli/pull/28/files#diff-083575b8cef39c5a3f9bb2f511938fcf314c5755c81f0073013fd70daf5243f1R57

but now it becomes a convention to have the dot notation? should it be enforced at some layer?

[brunocalza]

not yet, we can't kill it yet because the provider kind of depends on this semantics to create the namespace entry in the database. We can only kill it after remodeling the database tables (I'm planning to write a doc on how to do that remodeling, shouldn't be hard)

it's being enforced here in the CLI and here in the provider

[sanderpick]

Awesome. I left one comment about vault names, but maybe that is planned for the other renaming PR that you mentioned is planned.

[avichalp]

these are private fields but do we want to keep using the old names here or it doesn't matter?

[brunocalza]

yeah, makes sense to change to VaultsProvider and VaultsUploader, we can iterate on that on the next PRs

[avichalp]

👍

[avichalp]

Looks good!