Issue Summary:

The `forge version bulk-upgrade start` CLI command throws an unexpected error when a bulk upgrade attempt is ineligible (for e.g. due to scope changes)

While the bulk upgrade operation failing is expected behaviour, the CLI erroring out in this manner is not.

Steps to Reproduce

Step 1: Have a Forge app where a new version introduces additional scopes that constitute a privilege escalation (e.g., manage:servicedesk-customer).
Step 2: Attempt to run `forge version bulk-upgrade start` via the CLI.

Expected Results

The CLI should gracefully handle the privilege escalation case and inform the user that the bulk upgrade is not eligible due to scope escalation, without throwing an error. 

Using the interactive flow of `forge version bulk-upgrade start` should prompt the user with `There are no upgrade paths available`

Actual Results

The CLI errors out unexpectedly without surfacing the error with a clear, actionable message.

Workaround

Run `forge version compare` to check whether versions are eligible for bulk upgrades before attempting the operation.