Handle updated message that means "do a branch pipeline"

Still waiting to see if this fix works as I expect...

But basically, we only have branch pipelines. If the commits did not need additional tagging (no "fusion" required), and the CI pipeline was already in process, we would get this:

marge.gitlab.BadRequest: (400, {'message': {'base': ['Pipeline will not run for the selected trigger. The rules configuration prevented any jobs from being added to the pipeline.']}})

That more or less looks like they just changed the message, so that's what I treated it as.