The jstests/with_mongot/mongotmock/mongot_kill_cursors.js caused a hot BF in search_pinned_connections_auth suite because there isn't a way with mongot mock to avoid the race with the network (to issue the killCursor only after mongot has reponded to last getMore command).

The fix was to remove this test from the suite. 

It seems like the appropriate way to re-capture this coverage is by adding a unit test using networkInterfaceMock where we can ensure mongot replied to the getMore before issuing mongot a killCursor. Because this team owns TEC (and therefore un/pinned connections) we thought it made most sense for this team to own this work.