Fix Core retry API version after token renewal

[mesilov]

Q	A
Bug fix?	yes
New feature?	no
Deprecations?	no
Issues	Fix #544
License	MIT

Fixes Core::call() retry behavior after OAuth token renewal: when a request is repeated after an expired_token response, the retry now preserves the originally requested API version instead of falling back to ApiVersion::v1.

Additional changes:

• Added a regression unit test that verifies ApiVersion::v3 is preserved across the expired-token retry path.
• Added the currently available live scope codes timemanmobile and vibecodeconnector to Scope.
• Kept the current dependency gates green by updating the Rector config for Rector 2.6.1 and applying the Rector-requested PHPUnit mock attribute.

Test plan

• make oa-schema-build — passed
• make lint-cs-fixer — passed, 0/1090 files fixable
• make lint-rector — passed
• make lint-phpstan — passed, 2453 files, no errors
• make lint-deptrac — passed, 0 violations, 0 errors
• make test-unit — passed, 1222 tests, 3338 assertions
• Regression test testCallPreservesApiVersionAfterExpiredTokenRenewal — passed, 1 test, 2 assertions
• Live tests/Integration/Core/Credentials/ScopeTest.php — passed, 1 test, 1 assertion
• make test-integration-core — attempted twice; blocked by an unrelated live Bitrix24 operation limit in BatchTraversableListTest::testSingleBatchWithDescSortingMore during tearDown() cleanup via crm.contact.delete. The full-suite run reached 24 tests / 3174 assertions before that cleanup error, and the targeted retry reproduced the same external cleanup limit after 1 test / 2512 assertions.

Leftover contacts from the failed live runs were cleaned up by filtering on the failed-run ORIGINATOR_ID values; the final count check returned found=0 for both values.

Closes #544