chasquid: Return error on inaccessible private key file

In commit 3f9d0c0762, we added a new possible private file. If the file
exists but there's an error reading it (common for permission issues),
currently we just move on to the next file, and if it doesn't exist we
may give up with that error.

That can "hide" the access problems making them harder to debug.

To help with those kinds of errors, this patch updates the logic to
return an error if a private key exists but is inaccessible.

It also adds an unit test for this function to cover the different
scenarios, and updates the docs to match.

etc/chasquid/README

@@ -12,12 +12,13 @@ This directory contains chasquid's configuration.
 - certs/                 Certificates to use, one dir per pair.
   - example.com/
     - fullchain.pem  Certificate (full chain).
-    - privkey.pem    Private key.
+    - privkey.pem    Private key (can also be named key.pem).
   ...
 
 
 Note the certs/ directory matches certbot's structure, so if you use it you
 can just symlink to /etc/letsencrypt/live.
+The NixOS ACME module's layout (/var/lib/acme) is also supported.
 
 You need at least one certificate, or the server will refuse to start.
 Ideally there should be a certificate for each DNS name pointing to you.