fix: skip write body when status not allowed

[rogerogers]

What type of PR is this?

fix

What this PR does / why we need it (English/Chinese):

en: don't write body when status not allowed. According to the RFC definition https://www.rfc-editor.org/rfc/rfc9110.html#name-204-no-content, 204 and 304 response is terminated by the end of the header section; it cannot contain content or trailers.
zh: 状态码不允许存在body的时候不写入body。根据rfc定义，204、304还有其他几个状态码，不能设置响应body，这里跳过写入body。

Which issue(s) this PR fixes:

Fixes cloudwego/hertz#788

[kolinfluence]

@rogerogers it's not just status not modified.
possible to reference this?
https://stackoverflow.com/questions/8628725/comprehensive-list-of-http-status-codes-that-dont-include-a-response-body

also, it's "ok" to include body for custom status code. so i think it's ok to have body everywhere too.

[rogerogers]

https://cs.opensource.google/go/x/net/+/master:http2/http2.go;l=304
This is just a solution for this scenario. Writing a body to a status code that does not allow a body will cause the error.

[kolinfluence]

possible to expedite this merge?

[kolinfluence]

looks good to me

[rogerogers]

cc @wzekin

[kolinfluence]

pls just approve else 304 just crash. worst by doing nothing

[kolinfluence]

@rogerogers @welkeyever
pls update the release version too. thx

[rogerogers]

@rogerogers @welkeyever pls update the release version too. thx

You can use github.com/hertz-contrib/http2@962a08ada7d76a386c4b47a7d65cf75d0275c291 to perform your test. and update it when we release the new version