Define and communicate goals and non-goals of this project

[webmaster128]

There are multiple alternative approaches to CosmWasm build systems that come with different priorities and trade-offs.

E.g.

• Supporting private dependencies (Logic for handling git dependencies #82)
• Optimizing for incremental build speed (Support incremental workspace optimizations #84)
• Writing an alternative build system (https://github.com/mandrean/cw-optimizoor)

In order to guide future development and be able to confidentially reject PRs that are not in line, we should define goals and non-goals here.

[dakom]

In line with that high-level discussion, may I suggest to rename this project something like "contract builder"?

In other words, it seems to me that the goal of this project is really to have reproducible binaries, such that they can be confirmed by the on chain hash.

It's not to actually optimize wasm code, that's the goal of wasm-opt (and cargo itself)

Might seem a bit nitpicky, and naming things is hard, but it adds a bit of friction to discussions when I need to manually build for some reason, and it's unclear at first glance why I'm choosing to "not optimize" my contracts by skipping this tool (albeit while running cargo build and wasm-opt manually with the same exact settings as here).