test_Upgrade.py: add -Ov to the upgrade.sh invocation so the test's
intentional 2025.1->2025.2 upgrade doesn't get blocked by
check_p4_vs_sdp_version()'s safety abort (upgrade.sh line ~153): it
correctly detects that the P4 binary version being installed (2025.2,
the test's hardcoded --to-version default) is newer than the SDP's own
declared version (2025.1, from dev_rebrand's Version file, which is
itself a stale placeholder -- "Rev. SDP/MultiArch/2025.1/dev_rebrand
(YYYY/MM/DD)" -- never filled in for this branch).
This is a real, working safety check, not a bug -- the test just needs
to explicitly opt out of it (as -Ov is designed for), since the test's
purpose is exercising upgrade mechanics, not validating SDP/P4D version
compatibility policy. Bumping dev_rebrand's actual declared SDP version
is a real product decision (Task 4, SDP 2026.1 versioning work) and out
of scope here -- not touched.
Confirmed via manual reproduction (persistent container, no --rm) that
this was the exact and only preflight failure; verify_sdp.sh itself
reported 0 errors (1 pre-existing warning: no license file, expected in
this test environment).