Optimize node memory consumption

[fyrchik]

There is a number of cases where we can optimize the memory consumption.

• After SDK move all IDs should be passed by value where possible
• Fix/Do not use Prm pointers in Storage Engine #1418
• Fix/Do not use Res pointers in SE #1460
• Try to use metabase transaction context #1260
• Optimize object transformer pipelines: for a single object we consume C * size(object), ideally we'd like to have C = 1, using streaming interfaces, each separate transformer could be profiled
• Restrict the amount of concurrent service connections, return ErrBusy
• Support simple versioning for the metabase #1483
• Support simple versioning for the writecache #1501
• Do not use base58 strings as keys in the writecache #1473
• Do not use base58 strings as keys in the metabase #1482
• Optimize meta.ListWithCursor #1516

Anything else?

Related #1319 .

[carpawell]

Anything else?

Optimize GetRange of the FSTree? Now the blobstor reads the whole object via Get method, decompresses it, and only after that cuts the desired part of an object. Get method reads all the payload in the memory even if only a small part is required.

Optimization may require moving compression on the blobovnicza and FSTree levels and decompressing the object only if it was really compressed.

There is already some kind of thoughts about compression on the bloboznicza side:

neofs-node/pkg/local_object_storage/blobstor/blobovnicza.go

Lines 607 to 610 in f699e82

	// we don't use GetRange call for now since blobovnicza
	// stores data that is compressed on BlobStor side.
	// If blobovnicza learns to do the compression itself,
	// we can start using GetRange.

@nspcc-dev/neofs-core