Handle failed cherry-picks differently depending on failure reason
Now that gitlab-org/gitlab!19518 (merged) has been merged, we can update our cherry-picker to handle the :empty
state differently from the :conflict
state.
When it's empty, we can post a message saying so, and a message something like "It's likely this change already exists in the target and no further action is needed."