fix: ConnectedOrgVersion returns 9.0.0.0 with token-provider auth, causing false solution version incompatibility

[Copilot]

With --environment (interactive auth), ServiceClient is constructed via the token-provider constructor which defers connection initialisation until the first Execute call. Package Deployer reads CrmSvc.ConnectedOrgVersion during solution validation before any Execute has run, sees the default 9.0.0.0, and rejects solutions requiring CDS ≥ 9.1.

Changes

• CrmServiceClient.ConnectedOrgVersion (shim) — after the existing Execute(RetrieveVersion) warm-up attempt, re-read base.ConnectedOrgVersion. Calling Execute populates _connectionSvc.OrganizationVersion as a side-effect of connecting, so even when the RetrieveVersion response body can't be parsed the base property now reflects the real server version:

  // After try/catch for Execute(RetrieveVersion):
  var postWarmVersion = base.ConnectedOrgVersion;
  if (postWarmVersion > new Version(9, 0, 0, 0))
  {
      _cachedOrgVersion = postWarmVersion;
      return postWarmVersion;
  }

• PackageDeployerRunner.Run() — move ConnectedOrgVersion logging outside the if (_request.Verbose) guard. This pre-warms the version cache before Package Deployer reads it, and surfaces the org version in normal output — useful when diagnosing version mismatch errors.