add a deployment CI workflow

[jondot]

for each of the deployments, generate the deployment and make sure the app builds.

1. shuttle: build as a cargo build
2. docker: build a docker image

[kaplanelad]

@jondot,

Regarding Shuttle, I suggest we put it on hold until #1120 supports the new platform. If that issue isn’t resolved, we might need to remove Shuttle support in the next release.

For Docker, we're setting up the project (loco new) with the LOCO_DEV_MODE_PATH environment variable. In the Cargo.toml, we are pointing the loco-rs crate to a local path like this:

[workspace.dependencies]
loco-rs = { version = "*", path = "/PATH", default-features = false }

When running docker build as part of the CI process, I encounter the following error:

error: failed to load manifest for dependency `loco-rs`

I can’t run cargo build --release when the path isn’t included in the Dockerfile.

I could inject a COPY instruction to add the local path to the Docker image, that doesn't seem like the best solution.

WDYT?