Include development Gemma in the CI build matrix

[arteymix]

To ensure that Gemma.R is always working with upcoming features and improvements, it would be critical to include the development instance in its CI.

• whitelist GitHub Actions IP in the Apache configuration @dima-v-v
• add a different Gemma hostname to the build matrix @oganm
• trigger a build when Gemma development branch is deployed using some POST hook

The IP for GitHub Actions can be found in the docs. I'm on mobile now, so it's not exactly convenient to pull that information.

[oganm]

Workflow in the dev_test_workflow branch has a job pointing to the dev.gemma.msl now. currently this fails since actions machines aren't allowed to reach there yet.

[arteymix]

Good. I'll follow up with dima to get the IP ranges allowed.

[arteymix]

I sent this file to dima which contains all the Apache directives to allow GitHub Actions access to dev.gemma.msl.ubc.ca: github-actions.conf.txt.

[oganm]

Added the dev testing to the current branch but it's not currently working. Will poke dima again

A current version the file above can be generated by doing

gh::gh('/meta')$actions %>% unlist %>% paste('Require ip',.) %>% cat(file = 'file.txt',sep='\n')

github-actions.conf.txt