[#679] engine: Do not increase error counter on meta mismatch

It was introduced in 69e1e6ca to help node determine faulty shards.
However, the situation is possible in a real-life scenario:
1. Object O is evacuated from shard A to B.
2. Shard A is unmounted because of lower-level errors.
3. We now have object in meta on A and in blobstor on B. Technically we
   have it in meta on shard B too, but we still got the error if B goes
   to a degraded mode.

Signed-off-by: Evgenii Stratonikov <e.stratonikov@yadro.com>

pkg/local_object_storage/engine/range.go

@@ -5,6 +5,7 @@ import (
 	"errors"
 	"strconv"
 
+	"git.frostfs.info/TrueCloudLab/frostfs-node/internal/logs"
 	"git.frostfs.info/TrueCloudLab/frostfs-node/pkg/local_object_storage/shard"
 	"git.frostfs.info/TrueCloudLab/frostfs-node/pkg/local_object_storage/util"
 	"git.frostfs.info/TrueCloudLab/frostfs-node/pkg/local_object_storage/util/logicerr"
@@ -113,9 +114,10 @@ func (e *StorageEngine) getRange(ctx context.Context, prm RngPrm) (RngRes, error
 		if it.Object == nil {
 			return RngRes{}, it.OutError
 		}
-		if it.ShardWithMeta.Shard != nil {
-			e.reportShardError(it.ShardWithMeta, "meta info was present, but object is missing",
-				it.MetaError,
+		if it.ShardWithMeta.Shard != nil && it.MetaError != nil {
+			e.log.Warn(logs.ShardMetaInfoPresentButObjectNotFound,
+				zap.Stringer("shard_id", it.ShardWithMeta.ID()),
+				zap.String("error", it.MetaError.Error()),
 				zap.Stringer("address", prm.addr))
 		}
 	}