Draft: Set timeout from 300s to 3000s

What does this MR do and why?

Fix failed job about timeout: https://jihulab.com/gitlab-cn/gitlab/-/jobs/8489653

Gitlab::UsageDataMetrics.uncached_data with instrumentation_class Redis_HLL_counters is included in the Service Ping hash structure
     Failure/Error: known_events.map { |event| event[:name] }
     Timeout::Error:
       execution expired

为什么设置这么大的 timeout

1. 我们现在不知道一个刚刚好的时间是多少

   在本地验证的结果不可信，因为不同的机器的执行结果都不一样。@HiveerLi 测出来的是 600s，我测出来的是 300s。

2. 这是一个临时的改动。我们先保证 Pipeline 通过，之后再寻找问题的根本原因

   根本原因是指：是什么改动让这些测试突然变慢了这么多。

   在找到并解决根本问题之后，我们再将 timeout 改回 300s。

---

@HiveerLi: 根据本地日志，可以看出来这确实是一个执行超时的问题：

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before	After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.