session: fix tests to match updated node behavior

[roman-khimov]

This effectively reverts 603de8d, but current node returns 2048 again.

[roman-khimov]

See https://rest.fs.neo.org/HXSaMJXk2g8C14ht8HSi7BBaiYZ1HeWh2xnWPGQCg4H6/1473-1712080712/index.html#suites/fb2643933f3d9d19313b2e8b63c64bcd/ee0991ddcb38bc9a/

[cthulhu-rider]

what node issue/PR reversed the behavior? lets mention it in the commit, i cant follow the tracks

[roman-khimov]

That I can't say definitively now. Maybe @carpawell knows.

[roman-khimov]

In fact, it's nspcc-dev/neofs-node#2787.
a5ffb24d0aca15cce8ab6d5ca51aeebca2bf3a0e: https://rest.fs.neo.org/HXSaMJXk2g8C14ht8HSi7BBaiYZ1HeWh2xnWPGQCg4H6/1455-1711960969/index.html
0d6d5852c4e9518d547db8ea725b7dc8f0646eb3: https://rest.fs.neo.org/HXSaMJXk2g8C14ht8HSi7BBaiYZ1HeWh2xnWPGQCg4H6/1459-1711989386/index.html

[roman-khimov]

Maybe triggered by nspcc-dev/neofs-sdk-go@035b5ad?

[cthulhu-rider]

Maybe triggered by nspcc-dev/neofs-sdk-go@035b5ad?

if tests use CLI to sign session tokens (i bet they do), then yes

and maybe @carpawell opened nspcc-dev/neofs-sdk-go#546 while researching this test? There is also nspcc-dev/neofs-node#2731 which may relate one way or another

anyway, if test tries to prepare token with valid (!) format and signed from a party without access rights, then ACCESS_DENIED is an expected status. stranger_wallet in code hints