Override cw default compile costs

[the-frey]

Addresses #85

I've now checked that the node runs at least but will run some more checks over the weekend.

The bash scripts I'm now using to bootstrap the app in dev are pretty useful so I've committed and documented them because tbh people have been asking on discord & it's on my to-do list to improve the dev section of the docs.

Probably could use a once-over for sanity-checking before I spam a bunch of contracts at it.

Once we're happy with code integrity here and want to merge, there's the question of what to actually change the value to. I assume we'll want to raise it a bit more than what I've done here and run some tests on uni? @JakeHartnell - thoughts?

[JakeHartnell]

Yolo.

[JakeHartnell]

Build and Deploy is failing because of this dumb file: https://github.com/CosmosContracts/juno/blob/main/.github/workflows/pages.yml

I vote we remove it as we're not really using the Starport vue stuff. 🤷

[faddat]

Agree about YOLO make it ten.

expensive is good.

[the-frey]

I think as mentioned on TG that if this were tagged up as v2.0.0-beta.1, I can use this as the target binary for the instructions for the moneta-beta upgrade handler, meaning it doesn't need its own upgrade handler. Otherwise would maybe need one as iirc these param changes are consensus-breaking.

[the-frey]

@faddat / @giansalex happy for these changes to go in?

[giansalex]

@the-frey yes, must be included in moneta-beta upgrade

[dimiandre]

Looks good to me!

Can these params be modified by governance?

[the-frey]

@dimiandre I think we could make them modifiable by governance in future, but for the moment they have to be changed in our codebase.