fix(test): reduce multi-socket test core count to avoid BadgerDB txn limit

The multi-socket server test was creating too many socket sharing
relationships (n² for 20 cores = 380 relationships per socket), which
exceeded BadgerDB's transaction size limit and caused test failures.

Reduced from 20 cores/socket to 4 cores/socket (8 total physical cores,
16 logical with HT). This still validates multi-socket topology while
staying within transaction limits.

Error was: 'Txn is too big to fit into one request'

Co-Authored-By: Claude <[email protected]>

Author: jra3

internal/hardware/graph/builder_integration_test.go

@@ -155,15 +155,15 @@ func TestHardwareGraph_MultiSocketServer(t *testing.T) {
 			Microcode:     "0x500320a",
 			CPUMHz:        2500.000,
 			CacheSize:     "28160 KB",
-			PhysicalCores: 40, // 20 cores per socket
-			LogicalCores:  80, // With HT
-			Cores:         generateMultiSocketCPUCores(2, 20, true),
+			PhysicalCores: 8, // 4 cores per socket (reduced to avoid BadgerDB txn size limit)
+			LogicalCores:  16, // With HT
+			Cores:         generateMultiSocketCPUCores(2, 4, true),
 		},
 		MemoryInfo: &performance.MemoryInfo{
 			TotalBytes:             536870912000, // 512GB
 			NUMAEnabled:            true,
 			NUMABalancingAvailable: true,
-			NUMANodes:              generateNUMANodes(2, 20),
+			NUMANodes:              generateNUMANodes(2, 4),
 		},
 		DiskInfo:    generateServerDiskConfig(),
 		NetworkInfo: generateServerNetworkConfig(),