docs(admin): clarify SYS_NICE capability is Docker-specific

The existing warning about adding SYS_NICE for HEIC preview generation
did not make clear this only applies to Docker deployments. Users running
Imaginary outside Docker were confused by a Docker-specific instruction
that is irrelevant to their setup.

Rewrites the sentence to explicitly mention Docker, names both the CLI
flag and Compose key, and adds a note that this does not apply outside
Docker.

Fixes #11083

Signed-off-by: skjnldsv <skjnldsv@protonmail.com>

Author: skjnldsv

admin_manual/installation/server_tuning.rst

@@ -252,8 +252,10 @@ Nextcloud to use Imaginary by editing your ``config.php`` file:
 
    Make sure to start Imaginary with the ``-return-size`` command line parameter. Otherwise, there will be a
    minor performance impact. The flag requires a recent version of Imaginary (newer than v1.2.4).
-   Also, ensure to add the capability ``SYS_NICE`` via ``--cap-add=sys_nice`` or (for Compose)
-   ``cap_add: - SYS_NICE``, as it is required by Imaginary to generate HEIC previews.
+   Also, if running Imaginary in Docker, ensure to add the Docker container capability ``SYS_NICE``
+   via ``--cap-add=sys_nice`` (Docker CLI) or ``cap_add: - SYS_NICE`` (Docker Compose), as it is
+   required by Imaginary to generate HEIC previews. This is not applicable when running Imaginary
+   outside of Docker.
 
 .. note::