Add support for encrypting backups before uploading to S3 and decryptingduring restore. This includes:- Database schema changes:  - Added encryptionEnabled, encryptionMethod, and encryptionKey fields    to the destination table  - Created migration 0130_add_destination_encryption.sql- Server-side backup encryption:  - Added getEncryptionCommand/getDecryptionCommand utilities  - Updated all backup handlers (postgres, mysql, mariadb, mongo,    compose, web-server) to encrypt backups when enabled  - Encrypted backups have .enc extension appended- Server-side restore decryption:  - Updated all restore handlers to detect encrypted backups and    decrypt them during restore  - Added isEncryptedBackup utility to check file extensions- UI changes:  - Added encryption settings section to destination configuration  - Toggle for enabling/disabling encryption  - Dropdown for selecting encryption method (AES-256-CBC, AES-256-GCM)  - Input for encryption key with generate button  - Warning about storing keys securelyEncryption uses OpenSSL with PBKDF2 key derivation (100,000 iterations)for secure password-based encryption.

Replace OpenSSL-based encryption with rclone's native crypt backendfor better integration and simpler architecture. The crypt backendprovides transparent encryption/decryption using NaCl SecretBox(XSalsa20 cipher + Poly1305 for integrity).Changes:- Remove encryptionMethod field (rclone uses its own algorithm)- Add getRcloneS3Remote() to generate crypt-wrapped remotes- Simplify backup commands (encryption handled by rclone remote)- Simplify restore commands (decryption happens automatically)- Update UI to remove encryption method selection- Simplify migration to only add encryptionEnabled and encryptionKey

Add all rclone crypt configuration options to give users complete controlover backup encryption settings:New options:- password2: Optional salt password for additional security (recommended)- filenameEncryption: "standard", "obfuscate", or "off" (default: off)- directoryNameEncryption: Encrypt directory names when filename encryption is enabledUI improvements:- Added link to rclone crypt documentation- Password and salt password fields with generate buttons- Filename encryption dropdown with descriptions- Directory name encryption toggle (shown when filename encryption is enabled)Encryption details:- Uses NaCl SecretBox (XSalsa20 cipher + Poly1305)- Filename encryption uses EME for "standard" mode- All passwords should be stored securely as they cannot be recoveredSee:https://rclone.org/crypt/

Add comprehensive tests for getEncryptionConfigFromDestination andgetRcloneS3Remote functions covering all encryption options includingpassword2 (salt), filename encryption, and directory name encryption.

Resolved conflict in drizzle migration journal by renamingencryption migration from 0130 to 0131.

Update volume backup, restore, and cleanup functions to usegetRcloneS3Remote with encryption support. Volume backups nowrespect the destination's encryption settings (encryptionEnabled,encryptionKey, password2, filenameEncryption, directoryNameEncryption)just like database backups.