Ci Test: Ensure All RPC,GRPC,API, Websocket functions as expected

[hard-nett]

To ensure liveliness of all endpoints are available after major codebase upgrades, we can have test coverage of these possible by making use of various methods to test go-bitsong.

Test Implementations

• GRPC - cw-orchestrator tests + tonic (use GRPC to pass msgs)
• RPC - Bash scripting , Interchaintest
• API - Node/Javascript/Python
• Websocket - Node/Javascript/Python

Major Focal Points

• Every sdk module
• Packetforwardmiddleware
• tests: Wasm + IBC integration  #287
• fix: App Upgrade Local & CI Tests #288
• Init-from-state checks
• wasm conformance actions
• fix: PR & Upgrade CI #286
• feat: merge manual sh scripts into core repo #289

---

Testing Resources

LocalBitsong

Local bitsong deploys instances of bitsong for testing different scenarios on a local computer environment. #253 adds initial implementation, and we can build from here via reference to Osmosis' implementation

InterchainTest

Interchaintest is go scripts to deploy bitsong networks, via Docker images, for tests various scenarios. There are a number of existing templates and examples of ICT compatible with Bitsong, so these are able to be implemented

Cw-Orchestrator

Cw-Orchestrator is a rust scripting library, that makes writing interfaces for contracts and networks reusable for live, testnet, local, and simulation environments. #249 brought test for ibc-callbacks. These test require the use of Starship, a kubernetes container deployment system.

[hard-nett]

wasm query - #244 (comment)

[hard-nett]

A primary tool to use for testing go-bitsong functions is our KeeperTestHelper testing suite. This includes all of the objects necessary for simulating a bitsong environment in order to perform any test case we want.

Upgrades

In #252, an upgrade_test.go file is introduced, making use of our testing suite to simulate the upgrade process that resolves a bug with application. This format can be used in future upgrades to verify their functionalities.

GRPC Queries

One of the objects is the QueryHelper:

type KeeperTestHelper struct {
...
	QueryHelper *baseapp.QueryServiceTestHelper
}

This can also be used to verify any of our modules GRPC query functions.
Example:

#[tokio::main]
async fn main() -> Result<(), Box<dyn std::error::Error>> {
    let channel = tonic::transport::Channel::from_static("http://localhost:50051")
        .connect()
        .await?;

    let client = MyQueryClient {
        inner: bitsong::smartaccount::v1beta1::query_client::QueryClient::new(channel),
    };

    // Use `client` to make gRPC calls
    Ok(())
}