bundle/commands/exec: run check first

[carlocab]

• Have you followed the guidelines in our Contributing document?
• Have you checked to ensure there aren't other open Pull Requests for the same change?
• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your changes? Here's an example.
• Have you successfully run brew style with your changes locally?
• Have you successfully run brew typecheck with your changes locally?
• Have you successfully run brew tests with your changes locally?

---

brew bundle exec can behave wrongly if you haven't done brew bundle install
first. Let's run brew bundle check first to avoid this.

[MikeMcQuaid]

As said on #19637: prefer it due to performance regressions here. Thanks for opening both!

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.