Respect limit argument for PostgreSQL queries

I've been investigating slow queries for issues and issues-count. I've noticed that even though we use a limit of 10 and 100 respectively, these are not respected. For instance, if you load [this issue](https://sentry.sentry.io/issues/4386450198/events/8007adbaf541457994065a9857b65036/?project=1) you will see `limit 3001` in the message. If you click "Show More" you will that the variable `limit` says 100. [This code](https://github.com/getsentry/sentry/blob/41f334e1331c948bdef5e9a01b0b992a08692775/src/sentry/search/snuba/executors.py#L841-L843) is called with a limit of 3001 ([1](https://github.com/getsentry/sentry-options-automator/blob/main/options/regions/us/app.yaml#L12)) regardless of what value is passed to `limit` to the function. Here are some of the queries that would benefit from this (possibly more): [1](https://sentry.sentry.io/performance/database/spans/span/206fbe427e0d5381/?project=1&span.domain=sentry_groupedmessage&spansSort=-time_spent_percentage%28local%29&statsPeriod=14d), [2](https://sentry.sentry.io/performance/database/spans/span/8c45a55e025e14e7/?project=1&span.domain=sentry_groupedmessage&spansSort=-time_spent_percentage%28local%29&statsPeriod=14d), [3](https://sentry.sentry.io/performance/database/spans/span/4221b91474e96893/?project=1&span.domain=sentry_groupedmessage&spansSort=-time_spent_percentage%28local%29&statsPeriod=14d) and [4](https://sentry.sentry.io/performance/database/spans/span/791dd95469cfa43d/?project=1&span.domain=sentry_groupedmessage&spansSort=-time_spent_percentage%28local%29&statsPeriod=14d) I expect some of the issues in [here](https://sentry.sentry.io/discover/homepage/?field=count%28%29&field=count_unique%28issue%29&name=All+Events&project=1&query=error.type%3AOperationalError&sort=-count%28%29&statsPeriod=90d&yAxis=count%28%29) to improve: <img width="1052" alt="image" src="https://github.com/getsentry/sentry/assets/44410/532dfb0c-de94-43c4-8421-a16f34342ffe"> # Change * Create branch to use `[: limit + 1]` instea…