row: mark an error from streamer as StorageError

[yuzefovich]

Earlier this year we changed the vectorized panic-catcher, namely, we now check a few special error types (like StorageError, notInternalError, and internalError upfront - to avoid more expensive stack-based checks). If we find an internalError and it doesn't have a PG code and doesn't have StorageError or notInternalError in the causes, we now always mark the error as assertion failure. This made it so that we started receiving more sentry reports than previously; in particular, whenever we're using the streamer API, we could now get stop.ErrUnavailable via the following sequence of calls ColIndexJoin.Next -> cFetcher.StartScan -> txnKVStreamer.SetupNextFetch -> Streamer.Enqueue, and this would trigger a sentry report. This commit fixes this by marking an error coming from Streamer.Enqueue as StorageError which will by-pass the logic in the panic-catcher.

Fixes: #128649.

Release note: None

[blathers-crl[bot]]

It looks like your PR touches production code but doesn't add or edit any test code. Did you consider adding tests to your PR?

_{:owl: Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.}

[cockroach-teamcity]

This change is