kdump-utils-1.0.47-1 fails on remote ssh export. 

Using the following config : 

```
          ssh core@10.0.2.2
          sshkey /root/.ssh/id_ssh_kdump
          path /home/core/crash
          core_collector makedumpfile -F -l --message-level 1 -d 31
```

When triggering a kernel panic : 
```
         Starting kdump-capture.service - Kdump Vmcore Save Service...
[    2.308392] kdump[642]: Kdump is using the default log level(3).
[    2.239662] kdump[642]: Kdump is using the default log level(3).
[    3.344918] kdump[694]: saving to core@10.0.2.2:/home/core/crash/10.0.2.15-2024-10-14-13:01:14
[    3.276325] kdump[694]: saving to core@10.0.2.2:/home/core/crash/10.0.2.15-2024-10-14-13:01:14
[    3.351601] kdump.sh[696]: Warning: Identity file  /root/.ssh/id_ssh_kdump -o BatchMode=yes -o StrictHostKeyChecking=yes not accessible: No such file or directory
.
[    3.284293] kdump.sh[696]: Warning: Identity file  /root/.ssh/id_ssh_kdump -o BatchMode=yes -o StrictHostKeyChecking=yes not accessible: No such file or directory
.
[    3.375233] kdump[701]: saving vmcore status file to /vmcorestatus//var/crash/vmcore-creation.status
[    3.306658] kdump[701]: saving vmcore status file to /vmcorestatus//var/crash/vmcore-creation.status
[    3.378655] kdump[705]: saving vmcore failed
[    3.309817] kdump[705]: saving vmcore failed
[    3.380191] systemd[1]: kdump-capture.service: Main process exited, code=exited, status=1/FAILURE
[    3.311558] systemd[1]: kdump-capture.service: Main process exited, code=exited, status=1/FAILURE
[    3.381481] systemd[1]: kdump-capture.service: Failed with result 'exit-code'.
[    3.312776] systemd[1]: kdump-capture.service: Failed with result 'exit-code'.
[FAILED] Failed to start kdump-capture.service - Kdump Vmcore Save Service.
See 'systemctl status kdump-capture.service' for details.

```

Looking at this line : `Warning: Identity file  /root/.ssh/id_ssh_kdump -o BatchMode=yes -o StrictHostKeyChecking=yes not accessible: No such file or directory`
It looks like a quote is not escaped correctly.

Note that this is a regression because i cannot reproduce the issue in the exact same setup using kdump-utils-1.0.44-2.