Currently, our `perf-cost` experiment does not attempt to provide any cost estimations. We should provide this functionality, hardcode cloud costs per supported regions (or query them, if there's an API for it): - Function duration and memory costs - Function invocation costs - State transitions for workflows - Estimate storage accesses