enhance row count retrieval: add AWS-specific estimation and fallback mechanism

[Artuomka]

No description provided.

To fix the issue, we need to parse the host value and validate it against a whitelist of allowed AWS domains or patterns. Instead of using host.includes('amazonaws.com'), we should use a stricter check that ensures the host ends with .amazonaws.com and does not contain any unexpected subdomains. This can be achieved using a combination of URL parsing and regular expressions.

The fix involves:

1. Parsing the host value to ensure it is a valid domain.
2. Checking that the host ends with .amazonaws.com and matches expected patterns (e.g., *.amazonaws.com or ec2-*.compute.amazonaws.com).
3. Replacing the substring checks with these stricter validations.

---

To fix the problem, we should parse the host string and check if it matches exactly amazonaws.com or is a subdomain of amazonaws.com (e.g., cassandra.amazonaws.com, ec2-xx-xx-xx-xx.compute.amazonaws.com). This can be done by splitting the host into its labels and checking if the last two labels are amazonaws.com, or by using a regular expression that matches only valid AWS hostnames. The fix should be applied in the isAWSConnection method, replacing the substring check with a more robust check. No new dependencies are required, as this can be done with standard string or regex operations.

---