Add missing rows.Err() check in AWS consumeEntries

[roger2hk]

Here is the fix for the issue found by Go Analysis.

sql.Rows "rows" is used in Next loop at line 1198 without final check of rows.Err() sqlrowserr ([default](https://pkg.go.dev/golang.org/x/tools/go/analysis/passes/sqlrowserr))

---

for rows.Next() stops for two different reasons, and they're indistinguishable without an extra check:

• All rows have been consumed normally (the happy path).
• An error occurred mid-iteration — e.g. a network/connection drop, a query cancellation, a driver-level decoding failure, or a context timeout.

Why that's dangerous here specifically: this is the sequencing consume path. If the query is truncated early by an error, the code would happily treat a partial result set as "that's all there was", then go on to consume/integrate only some of the entries — or, if zero rows were read, return false, nil ("nothing to sequence") when actually the DB call failed. Silent data-correctness bug rather than a loud error.