[Feature]: Document and improve setup flow for Cloud Page user root assignment

[DenizAltunkapan]

Problem

New self-hosted setups still require an admin to manually update the Cloud Page database so each user gets a valid root_folder_path.

This is easy to miss and confusing for new users. Example: a user can log in to Vault Web, but Cloud Page does not work until an admin manually creates the storage folder and updates the DB path to /host-cloud/<username>.

Proposed solution

Document this setup step in a more visible place and consider a small setup helper or runbook flow.

Scope:

• explain why Cloud Page needs a per-user root path
• document host path vs container path clearly, e.g. /data/vault-users/alice vs /host-cloud/alice
• provide a safe example command for updating the user record
• add a checklist for DB reachable, cloud root configured, JWT secret matching, and reverse proxy access
• optionally add a script later that creates the folder and updates the DB for a username

Acceptance criteria

• The manual Cloud Page user root assignment is documented in the main deploy/setup flow.
• The docs include a clear example for creating the host folder and setting the container-visible DB path.
• The docs warn against using host paths inside the Cloud Page DB.
• A setup checklist covers Cloud root, DB, JWT secret, and reverse proxy basics.
• The issue leaves room for a future helper script without requiring a full installer.