test(managed-agent): declare v2 reader in cleanup-conflict MySql IT (#16372)

`HostedCleanupRetentionMySqlIT.cleanupAdmissionConflictIsReturnedOverHttpOnMySql`
expects 409 `managed_session_cleanup_conflict`, but its commit carries a
`hosted.cleanup` event, which `ManagedHostedRecoveryRecords.requiresVersionTwo`
classifies as requiring storage v2. `JournalCommit` then calls
`readerVersion.requireReadable(2)` before the cleanup-conflict check, and the
request never set the `X-Qwen-Managed-Max-Readable-Storage-Version` header, so
`ManagedSessionReaderVersion` defaulted the ceiling to 1 and threw
`managed_session_reader_version_unsupported` first. The 2026-11-04 nightly
failed on exactly that mismatch.

Declare the v2 reader ceiling (the same header `ManagedSessionStoreIntegrationTest`
uses when it expects the commit to be accepted) so the request reaches the
cleanup-admission path the test actually exercises.

Co-authored-by: Qwen-Coder <[email protected]>

packages/managed-agent-server/verification/src/test/java/com/alibaba/qwen/code/managedagent/HostedCleanupRetentionMySqlIT.java

@@ -50,6 +50,7 @@ class HostedCleanupRetentionMySqlIT extends HostedCleanupRetentionTest {
                         .header("Content-Type", "application/json")
                         .header(TenantContextFilter.HEADER, "tenant")
                         .header(ManagedSessionStoreModels.WRITER_TOKEN_HEADER, ExtensionRecordJournal.TOKEN)
+                        .header("X-Qwen-Managed-Max-Readable-Storage-Version", "2")
                         .POST(HttpRequest.BodyPublishers.ofString(json.writeValueAsString(request))).build(),
                         HttpResponse.BodyHandlers.ofString());
                 assertThat(response.statusCode()).as(route).isEqualTo(409);