Approved work lands when main is ahead of the remote

Approving a card could fail when its workspace was cloned from the remote and other cards had already landed on the local main without being pushed. Obeya showed a misleading message about local changes, and every new approval failed the same way. The work is now rebased onto main as the local checkout has it, so it lands. If landing is blocked by something outside the work, the card's agent hears about it too, so it no longer tells you the card is still waiting for approval as if nothing had happened.