Reword "recovering leaked sessions" log message.

The previous message implied the possible existence of leaked sessions, and could be confusing/alarming when reading log files. The new message is intended to imply that there could be some leaked sessions (but there may very well be none) and that detecting them will take a small amount of work.

Author: bgrainger

src/MySqlConnector/Core/ConnectionPool.cs

@@ -28,7 +28,7 @@ public async ValueTask<ServerSession> GetSessionAsync(MySqlConnection connection
 			// on the lock in RecoverLeakedSessions in high-concurrency situations
 			if (IsEmpty && unchecked(((uint) Environment.TickCount) - m_lastRecoveryTime) >= 1000u)
 			{
-				Log.Info("Pool{0} is empty; recovering leaked sessions", m_logArguments);
+				Log.Info("Pool{0} is empty; scanning for any leaked sessions", m_logArguments);
 				await RecoverLeakedSessionsAsync(ioBehavior).ConfigureAwait(false);
 			}