GC stops on metabase errors

[roman-khimov]

Expected Behavior

GC doing as much as it can.

Current Behavior

Apr 20 04:09:14 titan4 neofs-node[420363]: 2024-04-20T04:09:14.760Z warn shard/gc.go:339 iterator over expired locks failed {"shard_id": "2N1drpyfAuTXes7ShXUAF4", "error": "could not parse expiration epoch: strconv.ParseUint: parsing "'or'1'='1": invalid syntax"}

It just stopped at the first error.

Possible Solution

Log the error and go on, there are many objects that still can be deleted.

Steps to Reproduce (for bugs)

Add a broken object to the system (with __NEOFS__EXPIRATION_EPOCH=garbage), see how GC can't delete even correct ones.

Context

#2822.

Your Environment

• Version used: 0.41.0