Validate service project is correct when deploying
If someone forks a repo that is already using runway, and then does an action that would trigger runway, it would automatically deploy from their fork overwriting whatever was actually deployed from canonical.
To avoid this, we want to make sure we have a preflight check in the deployment repo that will validate that the project triggering the deploy is in fact the service project.
This can be done by checking the variable CI_PIPELINE_SOURCE
is parent_pipeline
and the variable SOURCE_PROJECT_ID
matches what we expect. This likely means making the provisioner populate a variable in the deployment repo of the "real" SOURCE_PROJECT_ID
so we know what's correct.