MG-72 - Fix NamedQueryContext not returning sql.ErrNoRows

[nnpvaan]

What type of PR is this?

This is a bug fix because it fixes the following issue: #72

What does this do?

• Fixes incorrect error handling when NamedQueryContext does not return sql.ErrNoRows.
• Ensures row.Next() is checked before calling StructScan().
• Returns repoerr.ErrNotFound wrapped with sql.ErrNoRows when there are no rows.

Which issue(s) does this PR fix/relate to?

• Related Issue Bug: NamedQueryContext does not return sql.ErrNoRows, causing incorrect error handling #72
• Resolves Bug: NamedQueryContext does not return sql.ErrNoRows, causing incorrect error handling #72

Have you included tests for your changes?

No (Existing tests should already cover this behavior. If needed, I can add specific tests.)

Did you document any new/modified feature?

No (Bug fix, no new documentation needed.)

Notes

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 56.35%. Comparing base (9c15ba6) to head (9154595).
Report is 4 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff             @@
##             main      #73       +/-   ##
===========================================
+ Coverage   30.12%   56.35%   +26.22%     
===========================================
  Files          89       19       -70     
  Lines       13198     2889    -10309     
===========================================
- Hits         3976     1628     -2348     
+ Misses       8752     1046     -7706     
+ Partials      470      215      -255     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.