Remove global X lock acquisition for renameCollection. This is because acquiring global lock in X mode can be blocked by prepared transactions. The enqueued global X lock can block oplog queries which need the global IS lock. If these oplog queries and the data replication are needed to satisfy the prepared transaction's write concern, then the prepare transaction and replication cannot make progress. Thus a deadlock occurs.
Alternatively, if removing global X lock is not an option, deprecate the usage or make sure it won't be blocked on prepare transactions.