chore(e2e-tests): update server aggregation error warning for latest alpha COMPASS-10839

[Anemy]

COMPASS-10839

Latest alpha now has a different error code when cancelling a sleep in a js function.

code: 279,
codeName: 'ClientDisconnect',
errmsg: 'error while executing at wasm backtrace: ... nanosleep ... MozJSScriptEngine::sleep ...
Caused by:
  wasm epoch interrupt: kill pending'

I think there was a similar fix we had to do on mongosh. Here's a link for that context mongodb-js/mongosh#2768 (comment) there was a server bug causing it to have different results than we get now
https://jira.mongodb.org/browse/SERVER-130767

Patch (latest alpha suite only runs on main commits) https://spruce.corp.mongodb.com/version/6a579e2e71d2eb0007e0338d/tasks?sorts=STATUS%3AASC%3BBASE_STATUS%3ADESC

Opening as a draft as I think the ClientDisconnect could be a false positive for other situations and I want to look into if this is the intended behavior or its a temporary bug with the new wasm engine in new alpha. Thread https://mongodb.slack.com/archives/C04PDS7GAFM/p1784141230556669

[Copilot]

Pull request overview

Updates an e2e server-warning allowlist to keep aggregation-cancellation tests stable against newer server alpha behavior, while preserving signal from unexpected server warnings.

Changes:

• Allows ClientDisconnect in addition to Interrupted for the relevant aggregate command executor warning (id === 23799) during cancellation.
• Adjusts the warning-filter predicate formatting in the affected test.