feat: resend payload of reoccuring client request

[caalador]

If the client request contains
the previous id and exactly the
same message content respond with
the same payload as previously.

Closes #20506

[github-actions]

Test Results

1 158 files  ± 0  1 158 suites  ±0   1h 38m 3s ⏱️ + 6m 25s
7 514 tests + 1  7 461 ✅ + 1  53 💤 ±0  0 ❌ ±0 
7 892 runs  +65  7 829 ✅ +65  63 💤 ±0  0 ❌ ±0 

Results for commit 5be342a. ± Comparison against base commit 3149de8.

This pull request removes 1 and adds 2 tests. Note that renamed tests count towards both.

com.vaadin.flow.server.communication.ServerRpcHandlerTest ‑ handleRpc_duplicateMessage_doNotThrow

com.vaadin.flow.server.communication.ServerRpcHandlerTest ‑ handleRpc_duplicateMessage_throwsResendPayload
com.vaadin.flow.server.communication.UidlRequestHandlerTest ‑ clientRequestsPreviousIdAndPayload_resendPreviousResponse

♻️ This comment has been updated with latest results.

[mcollovati]

Tested with a custom buggy UIDLRequestHandler that seldom drops a response, returning a 410 response code.
The change proved to work very well. When a response for an UIDL message does not reach the client, then the connection status indicator appears for a moment, but then when the request is re-sent, the client receives the correct response and all proceeds correctly.

[sonarqubecloud]

Quality Gate passed

Issues
11 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud