Optimize the decoding of generic http2

[finefuture]

What is the purpose of the change

When native http2 sends a request, it is possible to send 1-2 data frames:

1. The data frame is sent together with the endStream identifier
2. The data frame and endStream identifier are sent separately.

In the second case, when a data frame with the endStream identifier is received and the data is empty, the parameters will be set to null. Loss of parameters will cause the call to fail.

Receiving the end_stream flag means that the unary data stream is complete and can be decoded.

Brief changelog

Verifying this change

Checklist

• Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
• Each commit in the pull request should have a meaningful subject line and body.
• Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
• Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7
• Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
• Add some description to dubbo-website project if you are requesting to add a feature.
• GitHub Actions works fine on your own branch.
• If this contribution is large, please follow the Software Donation Guide.

[finefuture]

@AlbumenJ The rest protocol has been migrated to the dubbo-spi-extension project.

[finefuture]

@oxsean @icodening PTAL

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 38.80%. Comparing base (a12975a) to head (49bd9eb).
Report is 80 commits behind head on 3.3.

Additional details and impacted files

@@            Coverage Diff             @@
##              3.3   #14175      +/-   ##
==========================================
+ Coverage   38.55%   38.80%   +0.25%     
==========================================
  Files        1895     1730     -165     
  Lines       79272    75341    -3931     
  Branches    11528    11099     -429     
==========================================
- Hits        30560    29233    -1327     
+ Misses      44439    41969    -2470     
+ Partials     4273     4139     -134     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[oxsean]

Can you provider a test case? or how to test it?

[finefuture]

Can you provider a test case? or how to test it?

Okay, I will provider a demo later.

[finefuture]

@oxsean This is the demo: https://github.com/finefuture/triple-http2-demo/tree/main

[oxsean]

LGTM.

[icodening]

LGTM

[finefuture]

Native http2 does not support client stream and bi stream (streaming requests are not supported), so we only need to deal with unary and server streams, which means streaming responses are supported.

Receiving the end_stream flag means that the unary data stream is complete and can be decoded.

[sonarcloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud