New dApp templates to demonstrate Beaker & tooling integrations

[xBalbinus]

Currently, beaker only has the basic counter example. I believe there is a need to expand scaffolded-dApp variety to encourage more builders to build via a bit more structure. These additional examples can help demonstrate tooling (such as various requests for custom cosmwasm bindings) that you can integrate with beaker.

Current list

• tokenfactory (already done, just needs to make beaker compatible)
• Escrow test contract
• CW20 Pot

[iboss-ptk]

@xBalbinus IMO, I would like to keep the templates in the main Beaker repo as lean as possible, so without clear picture on how could it improves the journey, I would like to keep it out from the main repo.

After careful thought, I think I'm not really a fan of having more templates, since it's not really composable and people need to modify it quite a bit to suit their needs. At some point I might want to spend time on this composability problem, but not now.

And other reason is that, with the improvements that is coming soon, it could break the template, so the more templates to maintain, the slower these things will get implemented, so the template on the main repo should be easily evolved with the surrounding tool (mainly around code-gen related work)

Here is some of my opinions for the list:

• tokenfactory I think this one might make sense since it gives some building block to osmosis specific interaction. (this could evolve after having osmosis_std)
• Escrow test contract -> not sure how this one would help buidl-ers, could be good as examples, but not as template, I might be wrong, please let me know.
• CW20 Pot -> I think we tends to not promote cw20, so I don't think we should add that as a template. but for demonstration purposes, I think other cw-plus would help.

But with that being said, these templates can lives somewhere else, and add how to use custom template in the documentation. What do you think?

[xBalbinus]

Sounds good! I agree with most, if not all of the above. I think that I can make the tokenfactory one on another repository, beaker compatible. In the meantime, let's close this - when we think of other solutions for the composability problem, we can re-open another PR for that.

I believe how to use custom template was added to the docs via my other PR, but please lmk if that's not the case and I can add.