cleanup: remove obsolete deployment and installation scripts

Remove legacy scripts replaced by twelve-factor deployment workflow:

- application/share/bin/deploy-torrust-tracker-demo.com.sh
- application/share/bin/install.sh

These scripts have been superseded by the new infrastructure-based
deployment process:
- Configuration generation: infrastructure/scripts/configure-env.sh
- Deployment automation: infrastructure/scripts/deploy-app.sh
- Twelve-factor workflow: make infra-apply + make app-deploy

Also updated:
- application/README.md: Remove references to deleted scripts
- application/docs/deployment.md: Document new deployment workflow
- application/tests/test-unit-application.sh: Test remaining utility scripts

Benefits:
- Reduces maintenance burden
- Eliminates duplicate/conflicting deployment methods
- Simplifies codebase to focus on modern twelve-factor approach
- Removes potential confusion between legacy and new workflows

Author: josecelano

application/README.md

@@ -19,9 +19,7 @@ application/
 │       ├── torrust-tracker-grafana-dashboard.png
 │       └── do-firewall-configuration.png
 ├── share/                     # Application resources
-│   ├── bin/                  # Deployment and utility scripts
-│   │   ├── deploy-torrust-tracker-demo.com.sh
-│   │   ├── install.sh
+│   ├── bin/                  # Utility scripts
 │   │   ├── ssl_renew.sh
 │   │   ├── time-running.sh
 │   │   ├── tracker-db-backup.sh

application/docs/deployment.md

@@ -10,12 +10,32 @@ This document outlines the deployment process for the Torrust Tracker demo appli
 
 ## 2. Deployment Steps
 
+The Torrust Tracker Demo now uses a **twelve-factor app deployment workflow**
+that separates infrastructure provisioning from application deployment.
+
+### From Local Machine (Recommended)
+
+Use the automated deployment workflow from your local development machine:
+
+```bash
+# Deploy infrastructure and application (complete workflow)
+make infra-apply ENVIRONMENT=production
+make app-deploy ENVIRONMENT=production
+
+# Validate deployment
+make app-health-check ENVIRONMENT=production
+```
+
+### Manual Deployment on Server (Legacy)
+
+If you need to manually deploy on the server:
+
 1. **SSH into the server**.
 
 2. **Navigate to the application directory**:
 
    ```bash
-   cd /home/torrust/github/torrust/torrust-tracker-demo
+   cd /home/torrust/github/torrust/torrust-tracker-demo/application
    ```
 
 3. **Pull the latest changes** from the repository:
@@ -24,18 +44,15 @@ This document outlines the deployment process for the Torrust Tracker demo appli
    git pull
    ```
 
-4. **Run the deployment script**:
+4. **Deploy using Docker Compose**:
 
    ```bash
-   ./share/bin/deploy-torrust-tracker-demo.com.sh
+   # Use the persistent volume environment file
+   docker compose --env-file /var/lib/torrust/compose/.env pull
+   docker compose --env-file /var/lib/torrust/compose/.env down
+   docker compose --env-file /var/lib/torrust/compose/.env up -d
    ```
 
-   This script handles:
-
-   - Stopping services
-   - Rebuilding containers
-   - Starting services
-
 ## 3. Verification and Smoke Testing
 
 After deployment, verify that all services are running correctly.
@@ -45,7 +62,12 @@ After deployment, verify that all services are running correctly.
 Check the status of all Docker containers:
 
 ```bash
-docker compose ps
+# From local machine
+make app-health-check ENVIRONMENT=production
+
+# Or manually on server
+cd /home/torrust/github/torrust/torrust-tracker-demo/application
+docker compose --env-file /var/lib/torrust/compose/.env ps
 ```
 
 ### Application Logs

application/share/bin/deploy-torrust-tracker-demo.com.sh

@@ -149,25 +149,27 @@ test_deployment_scripts() {
         return 0
     fi
 
-    # Check for key deployment scripts
+    # Check for key utility scripts
     local key_scripts=(
-        "deploy-torrust-tracker-demo.com.sh"
+        "ssl_renew.sh"
+        "tracker-db-backup.sh"
+        "tracker-filtered-logs.sh"
     )
 
     for script in "${key_scripts[@]}"; do
         local script_path="${scripts_dir}/${script}"
         if [[ -f "${script_path}" ]]; then
             if [[ -x "${script_path}" ]]; then
-                log_info "Found executable deployment script: ${script}"
+                log_info "Found executable utility script: ${script}"
             else
-                log_warning "Deployment script exists but is not executable: ${script}"
+                log_warning "Utility script exists but is not executable: ${script}"
             fi
         else
-            log_warning "Deployment script not found: ${script}"
+            log_warning "Utility script not found: ${script}"
         fi
     done
 
-    log_success "Deployment scripts validation completed"
+    log_success "Utility scripts validation completed"
     return ${failed}
 }