feat: add wasm registry config to local deployment

[reecepbcups]

Summary

ref: Lay3rLabs/wavs-foundry-template#163

This allows a local only registry to be run for rapid iteration with a pre testnet/prod enviroment. This avoids the need to setup wa.dev API keys and just allows it to work for users.

NOTE: this means the template no longer uses the set-source-digest --wasm-digest <> command.

[dakom]

if it helps the template, let's get this in a.s.a.p.... but @reecepbcups for a follow-up issue:

1. where does the localhost port here come from? hardcoding 8090 feels kinda arbitrary
2. should this stuff as a whole (other than dynamic domain) not come from wavs.toml somehow?

[reecepbcups]

• 8090 is the default upstream for the wasi warg registry
• I thought about this last night as well. For now I don't think it's required. If a user is not using wa.dev or the localhost, idk what they are using that is warg compatible. Once we find a use case to support OCI registries (ghcr), then yes a wavs.toml would make sense. Until that use case comes up we can stick like so

[dakom]

ok cool, I opened #651 but stuck it on the 0.5.0 low-priority roadmap :)