Build node lists for container/object once per request

[cthulhu-rider]

Is your feature request related to a problem? Please describe.

container node sets are requested multiple times, at least for:

• ACL processing (

  neofs-node/pkg/services/object/acl/v2/classifier.go

  Line 39 in 6180c09

  isContainerNode, err := c.fsChain.InContainerInLastTwoEpochs(idCnr, reqAuthorPub)

  ,

  neofs-node/pkg/services/object/acl/v2/service.go

  Line 450 in 6180c09

  inContainer, err := b.nm.ServerInContainer(cnr)

  )

• neofs-node/pkg/services/object/get/get.go

  Line 65 in 6180c09

  nodeLists, repRules, ecRules, err := s.neoFSNet.GetNodesForObject(prm.addr)

• maybe more

the same is true about container info:

• neofs-node/pkg/services/object/acl/v2/service.go

  Line 515 in 6180c09

  cnr, err := b.containers.Get(idCnr)

• neofs-node/pkg/services/object/placement/service.go

  Line 297 in 6180c09

  cnr, err := x.containers.Get(x.id)

• ...

this is excessive. Better to consider the state consistent for the entire request lifetime

cache can amortize the waste of resources

Describe the solution you'd like

get any consistent data only when needed and only once

Additional context

#1803

[roman-khimov]

This is especially relevant in cases we need to modify (hence, copy) these lists (like OID mapping).