ci-cd to publish windows porter fix image

[smalho01]

I found a solution to running Option 2 of the setup guide on windows, follow these steps:

1. docker pull codexrems/fullstack_rems-windows:REMSvCurrent
2. docker run -v /var/run/docker.sock:/var/run/docker.sock -ti --name porter-windows-container codexrems/fullstack_rems-windows:REMSvCurrent (this will run a docker container in interactive mode, giving you access to the containers shell for the rest of the commands.

In the interactive docker shell, run:

3. porter mixins install docker (step 4 of https://github.com/mcode/REMS/blob/master/DockerProdSetupGuideForMacOS.md#install-docker-desktop-for-mac)
4. porter mixins install docker-compose (step 4 of https://github.com/mcode/REMS/blob/master/DockerProdSetupGuideForMacOS.md#install-docker-desktop-for-mac)
5. porter install fullstack_rems --param vsac_api_key=${vsac_api_key} --allow-docker-host-access --reference codexrems/fullstack_rems:REMSvCurrent (https://github.com/mcode/REMS/blob/master/DockerProdSetupGuideForMacOS.md#install-and-run-porter-application)

You should now see the REMS solution servers spinning up and coming online.

To shut everything down after using the prototype, run the following commands:

1. ctrl + c (exits running porter process)
2. porter invoke fullstack_rems --action stop --param vsac_api_key=${vsac_api_key} --allow-docker-host-access (https://github.com/mcode/REMS/blob/master/DockerProdSetupGuideForMacOS.md#stop-running-porter-application)
3. ctrl + d (exits the interactive shell and shuts down the extra container ran in step 2 of the set up

[kierk]

Worked on a fresh user install with some minor troubleshooting around permissions which I will include in the doc rework.