[#24171] YSQL: Adapt of the PgCatalogPerfTest.ResponseCacheMemoryLimi…

…t unit test for pg15

Summary:
The `PgCatalogPerfTest.ResponseCacheMemoryLimit` fails on `pg15` due to too restrictive check of some metrics (`pg_response_cache_gc_calls` and `pg_response_cache_entries_removed_by_gc`). The value of this metrics may varies due to different reasons in different Postgres releases. Possible reasons are the size of each cache entry and the number of such entries due to difference in catalog tables content.
Jira: DB-13058

Test Plan:
Jenkins

```
./yb_build.sh --gtest_filter PgCatalogPerfTest.ResponseCacheMemoryLimit
```

Reviewers: jason

Reviewed By: jason

Subscribers: smishra, yql

Tags: #jenkins-ready

Differential Revision: https://phorge.dev.yugabyte.com/D38495

src/yb/yql/pgwrapper/pg_catalog_perf-test.cc

@@ -536,8 +536,8 @@ TEST_F_EX(PgCatalogPerfTest, ResponseCacheMemoryLimit, PgCatalogWithLimitedCache
         }
         return static_cast<Status>(Status::OK());
       })).cache;
-  ASSERT_EQ(cache_metrics.gc_calls, 9);
-  ASSERT_EQ(cache_metrics.entries_removed_by_gc, 26);
+  ASSERT_GT(cache_metrics.gc_calls, 0);
+  ASSERT_GE(cache_metrics.entries_removed_by_gc, cache_metrics.gc_calls);
   auto response_cache_mem_tracker =
       cluster_->mini_tablet_server(0)->server()->mem_tracker()->FindChild("PgResponseCache");
   ASSERT_TRUE(response_cache_mem_tracker);