Merge status checks cause cascade action to fail!

[bakosa]

When merge status checks like Jenkins or bamboo build are required for PR merge on the branch protection, the action will fail to merge the PR. When this error happens, we handle it like a merge conflict which is wrong.

We should handle the 405 for conflicts specifically and raise a real failed issue in this case!!

We may want to look into making the flow do actual direct pushes to the branches instead of PRs UNLESS a conflict is hit, then open a PR. Maybe this is optional? idk... that is what BitBucket does as well....