Unify the way _socketsMap is populated

[czunker]

What is not working as you expected it?
We currently have two different ways, to fill the _socketsMap:

cnquery/_resources/packs/core/processes.go

Line 214 in 05e6754

p.Cache.Store("_socketsMap", &resources.CacheEntry{Data: socketsMap, Error: socketsErr})

and

cnquery/_resources/packs/core/port.go

Line 285 in 05e6754

processes.MqlResource().Cache.Store("_socketsMap", &resources.CacheEntry{Data: processesBySocket, Error: nil})

The implementation in port was introduced with #531.

The current assumption is, we could use the way it is done in port.go also in processes.go to only have one way of getting the information.

Where on the platform does it happen?
cnquery

[czunker]

This should be done after the plugin refactoring is done.

[arlimus]

Apart from the proposed improvements in #1928, I double-checked it against main on 6e2a951 and noticed (1) we only have one way of handling the internal ports list now (via processes2ports on mqlPorts) and (2) it is only modified by processesBySocket now