Only support SQL queries within standard methods

[utarwyn]

Updated the @creedengo/limit-db-query-results (GCI24) rule to only trigger warnings within standard methods used to execute SQL queries. Also added new test cases to verify the updated rule.

We'll be able to add wider support for variables and other libraries, but in the meantime it helps avoid false positives.

Fixes #61

[Copilot]

Pull Request Overview

This PR updates the limit-db-query-results rule to trigger warnings only for SQL queries executed through standard SQL client methods and revises the documentation and tests accordingly.

• Updated code examples in documentation to illustrate compliant and non-compliant SQL queries.
• Modified the rule implementation to check if the SQL query is invoked via standard SQL client methods.
• Updated tests to reflect the new behavior and added changelog entries for clarity.

Reviewed Changes

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

File	Description
eslint-plugin/docs/rules/limit-db-query-results.md	Updated documentation examples for non-compliant and compliant code.
eslint-plugin/lib/rules/limit-db-query-results.js	Introduced verification for standard SQL client methods usage.
eslint-plugin/tests/lib/rules/limit-db-query-results.js	Updated tests to use SQL client methods and validate the rule update.
CHANGELOG.md	Added changelog entries for the updated rule.

Comments suppressed due to low confidence (1)

eslint-plugin/lib/rules/limit-db-query-results.js:42

• The valid test case for 'SELECT TOP 5 * FROM products;' is not handled as a limiting clause. Consider adding 'TOP' to the limitingClauses array to prevent false positives.

const limitingClauses = ["LIMIT", "FETCH FIRST", "WHERE"];

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
90.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud