CLI - spacetime upgrade takes --yes instead of deprecated --force

[bfops]

Description of Changes

I missed making this change in #1752. This PR migrates spacetime upgrade to --yes as well.

API and ABI breaking changes

Yes, this breaks spacetime upgrade --force.

Expected complexity level and risk

1

Testing

$ cargo run -- upgrade 0.12.0 --yes
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.22s
     Running `target/debug/spacetime upgrade 0.12.0 --yes`
Finding version...done.
You're already running the latest version: 0.12.0
Skipping confirmation due to --yes
You are currently running version 0.12.0 of spacetime. The version you're upgrading to is 0.12.0.
This will replace the current executable at /mnt/nutera/work/localhd-symlinks/SpacetimeDBPrivate/public/target/debug/spacetime.
Skipping confirmation due to --yes
  Downloading update... 18.64MiB/18.64MiB (0s)