Need better tests to make sure that the git server api works as expected

[brianmoose]

We are currently updating GitLab frequently and we have no good way to actually test that the new server will behave in a good way.
Currently we would have to manually set up a test civet server to point at the test GitLab server and manually create merge requests and run jobs etc, then manually make sure everything works as expected.

This isn't as big an issue for GitHub since they don't change things as frequently as GitLab.

Currently, the Civet tests uses mock so that we don't actually hit the git server so that we can run tests offline and also have bad values, etc.

This would probably require using quite a bit more of the API than we currently use.