[Feature]: Document docker rootless limitations for agent

Welcome!

• I have searched open and closed feature requests to make sure this or similar feature request does not already exist.
• This is a feature request, not a bug report or support question.

Component

Agent

Description

I have had a number of problems getting my beszel-agent running on rootless docker (See #2320 for the latest). It works so much better as a native systemd service that I think it would be worth having a caution in the documentation that rootless docker users consider a native binary install.

In my case, when I switched from rootless docker to native systemd, with no specific configuration, I suddenly get all this extra data:

• Temperature sensors
• Fans
• Battery
• GPU power, usage, and VRAM
• ZFS
• S.M.A.R.T. data
• Systemd services

If you don't need those, rootless docker works fine, but I think the difference in capability is worth a note.

Motivation / Use Case

I think it would be helpful to make an informed decision of basic capabilities with rootless docker compared with the full suite of monitoring features available from a native client.