fix: fold timeout into scope query

[ferhatelmas]

What kind of change does this PR introduce?

Refactor for perf

What is the current behavior?

Right now, statement timeout is sent separately which introduces extra round trip.

What is the new behavior?

Delay until the first statement (set_config) and combine them together in the same query to reduce one round trip to db.

Additional context

Additionally, make query text for scope module level, and cache headers/jwt payload for multiple queries in the same connection.

[coveralls]

Coverage Report for CI Build 28108508086

Coverage increased (+0.05%) to 78.573%

Details

• Coverage increased (+0.05%) from the base build.
• Patch coverage: 4 uncovered changes across 1 file (39 of 43 lines covered, 90.7%).
• No coverage regressions found.

Uncovered Changes

File	Changed	Covered	%
src/internal/database/pg-connection.ts	43	39	90.7%

Coverage Regressions

No coverage regressions found.

---

Coverage Stats

Relevant Lines:	12158
Covered Lines:	10005
Line Coverage:	82.29%
Relevant Branches:	7019
Covered Branches:	5063
Branch Coverage:	72.13%
Branches in Coverage %:	Yes
Coverage Strength:	414.24 hits per line

---

💛 - Coveralls

[fenos]

It's an interesting approach, but it might beat us in case we never call setScope on a query, and expect the timeout to still work.

Not sure if it's worth the performance gain here (1ms or less) vs a bit of a hidden timeout logic

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[Copilot]

Pull request overview

Copilot reviewed 6 out of 6 changed files in this pull request and generated no new comments.

[ferhatelmas]

it might beat us in case we never call setScope on a query

that's fine and covered by a test