What type of PR is this?

fix

Check the PR title.

• This PR title match the format: <type>(optional scope): <description>
• The description of this PR title is user-oriented and clear enough for others to understand.
• 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.

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

en: hertz use http-body-slice's length to compare with MaxKeepBodySize to decide if keep it in request/response or put into requestBodyPool on ResetBody().

// ResetBody resets request body.
func (req *Request) ResetBody() {
	req.bodyRaw = nil
	req.RemoveMultipartFormFiles()
	req.CloseBodyStream() //nolint:errcheck
	if req.body != nil {
		if req.body.Len() <= req.maxKeepBodySize { // use Length to judge here
			req.body.Reset()
			return
		}
		requestBodyPool.Put(req.body) // big body will be put into buffer pool
		req.body = nil
	}
}

However, a big request body (.Len()>MaxKeepBodySize) which was firstly put into requestBodyPool is still likely to be used in subsequent request, even if the actually request data is small..

func (req *Request) BodyBuffer() *bytebufferpool.ByteBuffer {
	if req.body == nil {
		req.body = requestBodyPool.Get() // big body may be reused for small request
	}
	req.bodyRaw = nil
	return req.body
}

therefore, once the subsequent request finish and back to ResetBody() logic, although its body's Cap is much larger than Len, it will still be kept in request/repsponse, which may introduce memory leak.

zh(optional): 将 MaxKeepBody 的判定条件由 Len() 改成 Cap()

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

(Optional) The PR that updates user documentation: