refine_collection_shard_key_abort_on_stepup.js is a regression test for SERVER-48527 to make sure that the operation context keeps no session metadata from transactions aborted as part of step-up.

Calling a refine shard key is an indirect way to test such behavior because it internally executes a transaction on the config server.

Under PM-1965, all DDL operations are being modified to happen under a distributed lock, causing trouble for the test expecting distributed locks to be not used. Moreover, the transaction is probably going to be emulated soon with a read at clusterTime in order to move the logic on the primary shard (there is currently no support for transaction on the CSRS from shards).

This ticket is to test in a more direct way (e.g. with a unit test) that transaction metadata are discarded from the operation context on step-up.