Implements Feature #192

This PR introduces logic to deploy source artifacts directly to Cloud Run, bypassing the Cloud Build step.

How it works
Instead of building a container image from source, we upload a pre-packaged archive of the application directly to a Cloud Storage bucket. Cloud Run then mounts this archive and executes it on top of a specified base image. This approach results in dramatically faster deployment times.

Limitations & Conditions

The direct source deployment (skipping Cloud Build) automatically triggers only under these specific conditions:

1. Node.js Only: Currently restricted to Node.js applications.
2. No Dockerfile: The project must not have a Dockerfile. If a Dockerfile is present, we assume custom build logic is required and fall back to Cloud Build.
3. Start Script Required: The package.json must contain a valid start script (deploying will fail or fall back if missing).
4. Standard Base Image: Uses nodejs22 as the default base image for the runtime.
5. No Custom Runtime Support: The Node JS app should not have custom engine specified.

Other limitations of source deployed applications without build are described here.

Deployment Performance Comparison

Tested with a simple hello-world app

Timelines

With Cloud Build (130s)

Direct Source Deployment (24.24s)

Manual Testing:
Performed manual testing of application deployments with multiple dependencies, ensuring clean and efficient installation and the deployments were successful.