Add support for Cloud Functions

[grayside]

If #9 and #11 are pursued, developers might have the ability to deploy to Cloud Functions with something like sst --skip-until deploy and a customized deploy command like gcloud functions deploy.

However, first class support for Cloud Functions deployment would be even better.

To do this, it would be necessary to change the current implementation of support for Cloud Run to something with a more extension-oriented model. This way the Cloud Run and Cloud Functions implementations can live side-by-side and be selected by some flag or configuration option.

sst --platform=cloudfunctions --runtime=python38

Implementation Thoughts

In the golang-samples cloudrunci package there is a Platform interface, and each variation of Cloud Run has support in a central way.

In this case, it might be better to create a CloudRun struct with the methods, but then pass around interfaces for the discrete operations, such as Builder, Deployer, URILoopupper.

With this model it may be possible that the scope of this tool isn't really limited to "serverless".

---

This issue affects two categories in my review of the repository:

• Internals: Is the implementation efficient, effective, and maintainable?
• Scope: Does the tool have the breadth of features and flexibility to support reasonable testing needs?