Adding the internal transaction in the ClusterServerParameterRefresher caused bugs in a large number of telemetry tests and tests which use transactions and sessions. This is because these tests expect that the only transactions/sessions which exist are those created explicitly. This assumption is broken by the aforementioned refresher, which runs periodically and creates its own session and transaction. I used a failpoint, skipClusterParameterRefresh, to stop the refresher from running during these tests as a temporary measure, but these tests should be revisited to make them robust enough to handle these sorts of internally created transactions.