Rename AdventureLog to Voyage and add fork attribution

- Replace all AdventureLog references with Voyage across ~102 files
  (7 case variants: AdventureLog, adventurelog, Adventurelog, ADVENTURELOG,
  AdventUrelog, AdventureLOG, adventure-log, adventure_log)
- Rename brand, static, and documentation assets to use voyage naming
- Rename install_adventurelog.sh → install_voyage.sh
- Update README.md and voyage_overview.md to credit AdventureLog as
  the upstream project and Sean Morley as its original creator

documentation/docs/troubleshooting/login_unresponsive.md

@@ -1,6 +1,6 @@
 # Troubleshooting: Login and Registration Unresponsive
 
-When you encounter issues with the login and registration pages being unresponsive in AdventureLog, it can be due to various reasons. This guide will help you troubleshoot and resolve the unresponsive login and registration pages in AdventureLog.
+When you encounter issues with the login and registration pages being unresponsive in Voyage, it can be due to various reasons. This guide will help you troubleshoot and resolve the unresponsive login and registration pages in Voyage.
 
 1. Check to make sure the backend container is running and accessible.
 
@@ -15,4 +15,4 @@ When you encounter issues with the login and registration pages being unresponsi
    - Check that the `ORIGIN` variable in the frontend is set to the URL where the frontend is access and you are accessing the app from currently.
    - Check that the `CSRF_TRUSTED_ORIGINS` variable in the backend is set to a comma separated list of the origins where you use your backend server and frontend. One of these values should match the `ORIGIN` variable in the frontend.
 
-4. If you are still experiencing issues, please refer to the [AdventureLog Discord Server](https://discord.gg/wRbQ9Egr8C) for further assistance, providing as much detail as possible about the issue you are experiencing!
+4. If you are still experiencing issues, please refer to the [Voyage Discord Server](https://discord.gg/wRbQ9Egr8C) for further assistance, providing as much detail as possible about the issue you are experiencing!

documentation/docs/troubleshooting/nginx_failed.md

@@ -1,10 +1,10 @@
 # Troubleshooting: `Starting nginx: nginx failed!` in the Backend Container
 
 ::: tip
-As of 1-10-2024, this should be resolved in the latest version of AdventureLog. If you are still experiencing this issue, please reach out to the AdventureLog community on Discord or GitHub for further assistance.
+As of 1-10-2024, this should be resolved in the latest version of Voyage. If you are still experiencing this issue, please reach out to the Voyage community on Discord or GitHub for further assistance.
 :::
 
-The AdventureLog backend container uses a built-in Nginx container with a built-in nginx config that relies on the name `server` to be the service name of the backend container. If the Nginx service fails to start in the backend container, the whole backend service will keep restarting and fail to start.
+The Voyage backend container uses a built-in Nginx container with a built-in nginx config that relies on the name `server` to be the service name of the backend container. If the Nginx service fails to start in the backend container, the whole backend service will keep restarting and fail to start.
 
 **The primary reason for this error is changing the backend service name `server` to something different**
 
@@ -16,30 +16,30 @@ If you're experiencing issues with the Nginx service failing to start in the bac
 - The service name should be set to `server` in the `docker-compose.yml` file. For example:
   ```yaml
   server:
-    image: ghcr.io/seanmorley15/adventurelog-backend:latest
-    container_name: adventurelog-backend
+    image: ghcr.io/seanmorley15/voyage-backend:latest
+    container_name: voyage-backend
   ```
 
 ### 2. **To keep the backend service name different**:
 
 - If you want to keep the backend service name different from `server`, you can mount a custom Nginx configuration file to the backend container.
 
-  - Get the default Nginx configuration file from the AdventureLog repository:
+  - Get the default Nginx configuration file from the Voyage repository:
 
   ```bash
-  wget https://raw.githubusercontent.com/seanmorley15/AdventureLog/refs/heads/main/backend/nginx.conf
+  wget https://raw.githubusercontent.com/seanmorley15/Voyage/refs/heads/main/backend/nginx.conf
   ```
 
   - Update the `nginx.conf` file to replace all occurrences of `server` with your custom service name.
   - Mount the custom Nginx configuration file to the backend container in the `docker-compose.yml` file. For example:
     ```yaml
     server:
-      image: ghcr.io/seanmorley15/adventurelog-backend:latest
-      container_name: adventurelog-backend
+      image: ghcr.io/seanmorley15/voyage-backend:latest
+      container_name: voyage-backend
       volumes:
         - ./nginx.conf:/etc/nginx/nginx.conf
     ```
 
 ### 3. **Restart the Backend Container**:
 
-These steps should help you resolve the issue with the Nginx service failing to start in the backend container. If you continue to face issues, please reach out to the AdventureLog community on Discord or GitHub for further assistance.
+These steps should help you resolve the issue with the Nginx service failing to start in the backend container. If you continue to face issues, please reach out to the Voyage community on Discord or GitHub for further assistance.

documentation/docs/troubleshooting/no_images.md

@@ -1,8 +1,8 @@
-# Troubleshooting: Images Not Displayed in AdventureLog
+# Troubleshooting: Images Not Displayed in Voyage
 
-The AdventureLog backend container uses a built-in Nginx container to serve media to the frontend. The `PUBLIC_URL` environment variable is set to the external URL of the **backend** container. This URL is used to generate the URLs for the images in the frontend. If this URL is not set correctly or not accessible from the frontend, the images will not be displayed.
+The Voyage backend container uses a built-in Nginx container to serve media to the frontend. The `PUBLIC_URL` environment variable is set to the external URL of the **backend** container. This URL is used to generate the URLs for the images in the frontend. If this URL is not set correctly or not accessible from the frontend, the images will not be displayed.
 
-If you're experiencing issues with images not displaying in AdventureLog, follow these troubleshooting steps to resolve the issue.
+If you're experiencing issues with images not displaying in Voyage, follow these troubleshooting steps to resolve the issue.
 
 1. **Check the `PUBLIC_URL` Environment Variable**: