Add data-only build process

[AlexAxthelm]

Now that we are publishing a data-less docker image that is otherwise what we want for CTM, we can improve speed in getting images to testing by preparing a second dockerfile which overwrites the (empty) pacta-data and templates.transition.monitor directories.

Note, that I am imagining this as a testing-only image, but which can be used to quickly get images up to the BETA platform

[cjyetman]

I often test with the existing GHCR images, mounting in the templates and data, as per the README...

workflow.transition.monitor/README.md

Lines 115 to 140 in 39963af

	# Using Docker images pushed to GHCR automatically by GH Actions
	``` {.bash}
	tag_name=PR199
	repos_directory=~/github/rmi-pacta/
	data_folder=~/github/rmi-pacta/pacta-data
	# if you have local clones of workflow.transition.monitor and
	# templates.transition.monitor in the specified repos_directory above, you
	# probably do not need to edit any options below unless you want to further
	# customize things
	image_name=ghcr.io/rmi-pacta/workflow.transition.monitor:$tag_name
	portfolio_name="1234"
	user_folder=${repos_directory}workflow.transition.monitor/working_dir
	templates_folder=${repos_directory}templates.transition.monitor
	docker run -ti --rm --network none \
	--pull=always \
	--mount type=bind,source=${user_folder},target=/bound/working_dir \
	--mount type=bind,readonly,source=${data_folder},target=/pacta-data \
	--mount type=bind,readonly,source=${templates_folder},target=/templates.transition.monitor \
	$image_name \
	/bound/bin/run-r-scripts "$portfolio_name"
	```

[AlexAxthelm]

Yep. I'm basically extending that to include grabbing a dataset from AFS, and a branch from templates.transition.monitor, and baking that into a latest image that we can put on BETA.