Remote sync asks to push nonexistent changes before returning to main

## Title

Remote sync asks to push nonexistent changes before returning to main

## Description of the bug

Remote sync sometimes asks to push changes, then reports `skipped push: no changes` instead of taking the user directly back to `main`. It can also take much longer than shown in the [video]().

## Reproduction steps

1. Recently push changes from another branch in the same instance.
2. Return to the flow that should take the user back to `main`.
3. Observe that it asks to push changes and then says `skipped push: no changes`.

## Expected behavior

It should take the user directly to `main` without asking to push changes that do not exist.

## Logs

None.

## Diagnostic information (including Metabase version)

* Version: `master`

## Severity

* P3

Start by reproducing the remote sync flow described in the issue, then search the codebase for the `skipped push: no changes` message and trace the return-to-`main` path. Done means the flow returns directly to `main` without prompting for a nonexistent push, and the existing relevant tests pass or a regression test covers this behavior.

Written by the indexing model from the issue text.