[Feature]: PiKVM Agent Support

What is the installation method of your PatchMon server?

Docker

What is the version of your PatchMon server?

2.0.2

Briefly describe the feature

PiKVM Agent Support

Detailed description

So Patchmon agent installs fine on PiKVM.

Only a couple of issues here's the first one:

<img width="1680" height="317" alt="Image" src="https://github.com/user-attachments/assets/748d918f-d148-4606-9516-010628e34eab" />

As you can see because PiKVM file system is read-only so it can't write the to the log file ever. However it reports back to the Patchmon server no issues.

In the Patchmon Server it's impossible to Auto Update the Agent because the file system is read-only so I have to log into the PiKVM and run patchmon-agent update-agent in the cmd line.

<img width="1996" height="582" alt="Image" src="https://github.com/user-attachments/assets/47c8a5a7-e6f8-4ce6-bf1e-0de1cd249cc0" />

Finally the Patching via Patchmon fails for the same reason as the file system is read-only

<img width="1062" height="541" alt="Image" src="https://github.com/user-attachments/assets/4d18c818-a77e-4f90-8046-519f38438183" />

And the way PiKVM updates is using the pikvm-update wrapper script and it looks like this:

<img width="1874" height="662" alt="Image" src="https://github.com/user-attachments/assets/9d81e323-b04b-411f-aeb8-6a6c7c252dbd" />

I would imagine the easiest solution for the 2nd point is to have Patchmon agent run the command rw command, do the task, then ro to switch it back to read-only:

<img width="252" height="168" alt="Image" src="https://github.com/user-attachments/assets/51455c1c-d28a-4714-a2ed-f70d2d8b41b5" />

Why is this useful?

PiKVM gets a lot of updates due to them running on Arch Linux, so far it's very handy to see in Patchmon Server when they require updating and it's worth keeping them up to date since they connect to sensitive equipment.

As you can see I have plenty of PiKVMs in production so I am happy to do any testing if needed.