[2.x] Influx replication (OSS 2.4) stops working but still returns 204 status codes

__Steps to reproduce:__
1. Installed Influx OSS 2.4 on local edge computer and cloud enterprise.
2. Set up remote and replication to cloud

__Expected behavior:__
Local Influx to replicate to cloud.

__Actual behavior:__

- Local influx replicates to cloud for a while (sometimes even days). For an unknown reason it will stop replicating but still show status code 204 when viewing the "influx replication list" on the CLI.

- Current Queue bytes continues to grow indefinitely.

- It would be helpful if there was a way to restart the replication without having to delete and create it again.

__Environment info:__
SYSTEM INFO
OS Name: Microsoft Windows 10 Pro
OS Version: 10.0.19044 N/A Build 19044
System Model: HP EliteDesk 800 G2 DM 35W
System Type: x64-based PC
Processor(s): 1 Processor(s) Installed.
[01]: Intel64 Family 6 Model 94 Stepping 3 GenuineIntel ~2496 Mhz
BIOS Version: HP N21 Ver. 02.22, 3/27/2017
System Locale: en-us;English (United States)
Input Locale: N/A
Time Zone: (UTC-06:00) Central Time (US & Canada)
Total Physical Memory: 15,785 MB
Available Physical Memory: 11,949 MB
Virtual Memory: Max Size: 18,217 MB
Virtual Memory: Available: 14,386 MB
Virtual Memory: In Use: 3,831 MB

INFLUX VERSION
C:\windows\system32>influxd version
InfluxDB v2.4.0 (git: de247bab08) build_date: 2022-08-18T19:41:41Z

No source file or test is named. Start by reproducing the Influx OSS 2.4 remote and replication setup, then inspect the CLI's "influx replication list" status and queue behavior; done means replication failures are reported accurately and the replication can recover without deleting and recreating it.

Written by the indexing model from the issue text.