Use Pulumi directly instead of SST #57
Description
SST provides the perfect high level of abstraction a project like beet needs but the sst.config.ts workflow is very 'magical', for example:
- It doesn't allow for us to create a deno utility package that could read the
beet.toml. - It refuses to deploy without first building a crate, even though the config for that is severly limited. We're currently hacking around this with a two step deployment process that first deploys a dummy crate.
It seems most of the awesome parts we need are in @sst/platform so we could start by looking into using some of these high level components with pulumi directly.