Expand session token statuses #289
Description
Is your feature request related to a problem? Please describe.
I'm always frustrated when I see regular problems but cannot assign some well-known status to them. Session token is a good well-structed candidate. We did it once: #191. Now we also have validation on the SN side and now such errors can be seen by a user: nspcc-dev/neofs-node#2731, nspcc-dev/neofs-node#2727.
Describe the solution you'd like
Possible status codes:
- Wrong token issuer/not signed by container owner
- Invalid signature
- Wrong session operation
- Wrong container
Describe alternatives you've considered
Not sure all of them (or any of them) are required and having a separate code for them can make user's life easier but for the tests a well structured response for such an important NeoFS part may look pretty.