refactor: consolidate builds

[lumtis]

Description

WIP

Closes: #1331

[github-actions]

!!!WARNING!!!
nosec detected in the following files: contrib/localnet/orchestrator/smoketest/main.go, contrib/localnet/orchestrator/smoketest/test_accounting.go, contrib/localnet/orchestrator/smoketest/test_bitcoin.go, contrib/localnet/orchestrator/smoketest/test_deposit_eth.go, contrib/localnet/orchestrator/smoketest/test_stress.go, contrib/localnet/orchestrator/smoketest/test_update_bytecode.go, contrib/localnet/orchestrator/smoketest/test_zeta_in_and_out.go, contrib/rpctest/main.go, rpc/namespaces/ethereum/debug/api.go, rpc/namespaces/ethereum/debug/trace.go, rpc/namespaces/ethereum/debug/utils.go, rpc/websockets.go, server/start.go, testutil/network/util.go, x/observer/module_simulation.go, zetaclient/bitcoin_client.go, zetaclient/inbound_tracker.go, zetaclient/config/config_chain.go

Be very careful about using #nosec in code. It can be a quick way to suppress security warnings and move forward with development, it should be employed with caution. Suppressing warnings with #nosec can hide potentially serious vulnerabilities. Only use #nosec when you're absolutely certain that the security issue is either a false positive or has been mitigated in another way.

Only suppress a single rule (or a specific set of rules) within a section of code, while continuing to scan for other problems. To do this, you can list the rule(s) to be suppressed within the #nosec annotation, e.g: /* #nosec G401 */ or //#nosec G201 G202 G203
Broad #nosec annotations should be avoided, as they can hide other vulnerabilities. The CI will block you from merging this PR until you remove #nosec annotations that do not target specific rules.

Pay extra attention to the way #nosec is being used in the files listed above.