BasicACLErr and eACLErr errors are created incorrectly

[Ayrtat]

Expected Behavior

An error created by the method basicACLErr or eACLErr must be able to be casted to

var errAccessDenied *apistatus.ObjectAccessDenied

Current Behavior

It seems getObject method for object service works incorrectly here because the casting errors.As(err, &errAccessDenied) doesn't work out

Possible Solution

https://github.com/nspcc-dev/neofs-node/blob/master/pkg/services/object/acl/v2/errors.go#L28
https://github.com/nspcc-dev/neofs-node/blob/master/pkg/services/object/acl/v2/errors.go#L35
var errAccessDenied apistatus.ObjectAccessDenied should be replaced with errAccessDenied := &apistatus.ObjectAccessDenied{}

Steps to Reproduce (for bugs)

You can check it with unit-test

func TestBasicACLErr(t *testing.T) {
	var reqInfo RequestInfo
	err := basicACLErr(reqInfo)

	var errAccessDenied *apistatus.ObjectAccessDenied

	require.ErrorAs(t, err, &errAccessDenied,
		"basicACLErr must be able to be casted to apistatus.ObjectAccessDenied")
}

[cthulhu-rider]

these code spaces are executed on different processes - this on one node-as-client, this on another node-as-server. So, type mismatch must not affect behavior

[roman-khimov]

I think we can still check our error.As uses and try converting them to error.Is using new SDK types and instances, those work fine both for simple instances and pointers. And the code will likely be a bit more readable this way.

[Ayrtat]

these code spaces are executed on different processes - this on one node-as-client, this on another node-as-server. So, type mismatch must not affect behavior

Sorry, I didn't get the point. The client code invokes PayloadRange that gets a response from server side. And server returns wrapped basicACLErr error that is failed to get casted to apistatus.ObjectAccessDenied

[cthulhu-rider]

@Ayrtat i mean this calls client method and it must handle client's claimed return no matter what the server returns

as @roman-khimov said, we just inaccurately updated to a NeoFS SDK RC-9 that changed the documentation of returned errors: actual instead of previous

i suppose there may be other problem cases related to status error handling, lets resolve all of them in this issue