Memory assertion and INFO regressions following multi-DB support

[prvyk]

Describe the bug

LPUSH a b
PFCOUNT a
SELECT 0

fail: GarnetServer[0] Error disposing RespServerSession Tsavorite.core.TsavoriteException: Attempting to return an already-free block    at Tsavorite.core.SectorAlignedMemory.set_Free(Boolean value) in /garnet/libs/storage/Tsavorite/cs/src/core/Utilities/BufferPool.cs:line 80    at Tsavorite.core.SectorAlignedMemory.Dispose() in /garnet/libs/storage/Tsavorite/cs/src/core/Utilities/BufferPool.cs:line 126    at Garnet.server.StorageSession.Dispose() in /garnet/libs/server/Storage/Session/StorageSession.cs:line 105    at Garnet.server.RespServerSession.Dispose() in /garnet/libs/server/Resp/RespServerSession.cs:line 326    at Garnet.server.GarnetServerTcp.DisposeMessageConsumer(INetworkHandler session) in /garnet/libs/server/Servers/GarnetServerTcp.cs:line 248

Another regression is in INFO output. As I noted in #1019 (comment), some poor clients get stuck when section names have spaces (or any word separator).

This helps:

diff --git a/libs/server/Metrics/Info/GarnetInfoMetrics.cs b/libs/server/Metrics/Info/GarnetInfoMetrics.cs
index 52b02f488..2215da792 100644
--- a/libs/server/Metrics/Info/GarnetInfoMetrics.cs
+++ b/libs/server/Metrics/Info/GarnetInfoMetrics.cs
@@ -383,6 +383,8 @@ namespace Garnet.server
 
         public static string GetSectionHeader(InfoMetricsType infoType, int dbId)
         {
+	     // No word separators inside section names, as some clients will then fail to process INFO output!
+	     // https://github.com/microsoft/garnet/pull/1019#issuecomment-2660752028
             return infoType switch
             {
                 InfoMetricsType.SERVER => "Server",
@@ -390,13 +392,13 @@ namespace Garnet.server
                 InfoMetricsType.CLUSTER => "Cluster",
                 InfoMetricsType.REPLICATION => "Replication",
                 InfoMetricsType.STATS => "Stats",
-                InfoMetricsType.STORE => $"MainStore (DB {dbId})",
-                InfoMetricsType.OBJECTSTORE => $"ObjectStore (DB {dbId})",
-                InfoMetricsType.STOREHASHTABLE => $"MainStoreHashTableDistribution (DB {dbId})",
-                InfoMetricsType.OBJECTSTOREHASHTABLE => $"ObjectStoreHashTableDistribution (DB {dbId})",
-                InfoMetricsType.STOREREVIV => $"MainStoreDeletedRecordRevivification (DB {dbId})",
-                InfoMetricsType.OBJECTSTOREREVIV => $"ObjectStoreDeletedRecordRevivification (DB {dbId})",
-                InfoMetricsType.PERSISTENCE => $"Persistence (DB {dbId})",
+                InfoMetricsType.STORE => $"MainStore_DB_{dbId}",
+                InfoMetricsType.OBJECTSTORE => $"ObjectStore_DB_{dbId}",
+                InfoMetricsType.STOREHASHTABLE => $"MainStoreHashTableDistribution_DB_{dbId}",
+                InfoMetricsType.OBJECTSTOREHASHTABLE => $"ObjectStoreHashTableDistribution_DB_{dbId}",
+                InfoMetricsType.STOREREVIV => $"MainStoreDeletedRecordRevivification_DB_{dbId}",
+                InfoMetricsType.OBJECTSTOREREVIV => $"ObjectStoreDeletedRecordRevivification_DB_{dbId}",
+                InfoMetricsType.PERSISTENCE => $"Persistence_DB_{dbId}",
                 InfoMetricsType.CLIENTS => "Clients",
                 InfoMetricsType.KEYSPACE => "Keyspace",
                 InfoMetricsType.MODULES => "Modules",

Steps to reproduce the bug

LPUSH a b
PFCOUNT a
SELECT 0

Expected behavior

No response

Screenshots

No response

Release version

v1.0.62 + 0fe4bc6

IDE

No response

OS version

Linux/x86_64

Additional context

No response