fix: hertz panic when edit ctx.Params on HandleFunc

[3DRX]

What type of PR is this?

fix

Check the PR title.

• [x] This PR title match the format: \<type>(optional scope): \<description>
• [x] The description of this PR title is user-oriented and clear enough for others to understand.
• [x] Attach the PR updating the user documentation if the current PR requires user awareness at the usage level. User docs repo

(Optional) Translate the PR title into Chinese.

修复因用户在 HandleFunc 中修改 ctx.Params 值导致的 panic

(Optional) More detailed description for this PR(en: English/zh: Chinese).

en: This panic is happening because RequestContext.ResetWithoutConn only reset the length of Params (slice), not the array itself. Therefore, if the Params is re-assigned to another array by the user, it is possible that the capacity is not enough, leading to an out of bound array index. To fix this, we need to compare the current capacity and the expected capacity in RequestContext.ResetWithoutConn, and if they do not match, realloc Params. zh(optional):

(Optional) Which issue(s) this PR fixes:

Fixes #1149

(Optional) The PR that updates user documentation:

[CLAassistant]

All committers have signed the CLA.

[Duslia]

把 reset 里的逻辑挪到这里判断吧 https://github.com/cloudwego/hertz/blob/develop/pkg/route/engine.go#L753。这里是离使用最近的一个地方，怕还有其他的地方有一些错误使用，导致这里 panic 了。

[3DRX]

把 reset 里的逻辑挪到这里判断吧 https://github.com/cloudwego/hertz/blob/develop/pkg/route/engine.go#L753。这里是离使用最近的一个地方，怕还有其他的地方有一些错误使用，导致这里 panic 了。

改了，由于这个逻辑移动到了 RequestContext 外部，因此添加了 GetParamsCount 函数来访问 Params 原有的长度。