Gitlab::Git errors leak from some Commits::ChangeService

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

The Commits::ChangeService calls out to Repository directly.

If we pass a non-existent start_branch into the Commits::CherryPickService or Commits::RevertService, the services raise a Gitlab::Git::CommandError.

I believe we should wrap those errors using a call to BaseService#error so it can be dealt with from the caller.

Edited by 🤖 GitLab Bot 🤖