[Test only]

Issue

The rename_collection_cross_db_opposite.js jstest is designed to detect potential deadlocks in renameCollection between two databases.

However the test both sets a maxTimeMS for renameCollection and tolerates a MaxTimeMSExpired error.

Therefore even lock ordering were incorrect (i.e.  potential deadlock in production), the command would eventually consume its maxTimeMS, and the test would still succeed.

Fix

Consider removing MaxTimeMSExpired from the error list.