Fix incorrect markdown file paths in documentation views

- Updated `fetch` paths in legacy views (getting-started, upload-content, about, roadmap, community-guidelines, links) to point to the correct locations in `content/docs/`.
- Added debug logging to `js/docsView.js` to assist in diagnosing "Loading content..." hangs in the new documentation system.

Co-authored-by: PR0M3TH3AN <[email protected]>

views/getting-started.html

@@ -30,7 +30,7 @@
     const loadMarkdown = async () => {
       try {
         // Fetch the Markdown file
-        const response = await fetch("content/getting-started.md");
+        const response = await fetch("content/docs/getting-started.md");
         if (!response.ok) {
           throw new Error("Failed to load getting-started.md");
         }