TestKmeshRestart flaky

[hzxuzhonghu]

I have seen this case failure in E2E ipv6 test

https://github.com/kmesh-net/kmesh/actions/runs/12791951275/job/35661259039?pr=1191

=== RUN   TestKmeshRestart
2025-01-15T16:00:00.679713Z	info	tf	=== BEGIN: Test: '_home_runner_work_kmesh_kmesh_test_e2e[TestKmeshRestart]' ===
2025-01-15T16:00:10.706423Z	info	tf	Checking pods ready...
2025-01-15T16:00:10.708184Z	info	tf	  [ 0]                                   kmesh-mdjbj         Running (Ready)
2025-01-15T16:00:10.708201Z	info	tf	  [ 1]                                   kmesh-v9n42         Running (Ready)
    restart_test.go:65: Minimum success threshold, 1.000000, was not met. 312/313 (0.996805) requests failed: 1 error occurred:
        	* request 221: failed calling enrolled-to-kmesh (cluster=cluster-0)->'[http://service-with-waypoint-at-service-granularity.echo-1-83636.svc.cluster.local:80](http://service-with-waypoint-at-service-granularity.echo-1-83636.svc.cluster.local/)': call failed from enrolled-to-kmesh (cluster=cluster-0) to [http://service-with-waypoint-at-service-granularity.echo-1-83636.svc.cluster.local:80](http://service-with-waypoint-at-service-granularity.echo-1-83636.svc.cluster.local/) (using http): expected no error, but encountered rpc error: code = Unknown desc = 1/1 requests had errors; first error: Get "[http://service-with-waypoint-at-service-granularity.echo-1-83636.svc.cluster.local:80](http://service-with-waypoint-at-service-granularity.echo-1-83636.svc.cluster.local/)": read tcp [fd00:10:244:1::19]:52686->[fd00:10:244:1::a]:15019: read: connection reset by peer