Refactor Project Structure and Comprehensive Documentation Update

[ppant]

This PR performs a comprehensive cleanup and standardization of the repository's documentation and structure.

Key changes:

1. Naming Convention Standardization:

   • Renamed deque/ to Deque/ and Error-debug/ to ErrorHandling/.
   • Renamed Python scripts in Arrays/, LinkedLists/, Stacks/, and Trees/ to follow the PascalCase convention (e.g., Anagram_Check_Sorted_Sol.py to AnagramCheckSortedSol.py).
   • Corrected typos in filenames (e.g., BalanceParenthlessCheckImple.py to BalanceParenthesesCheckImple.py).

2. Documentation Enhancements:

   • The root README.md now serves as a complete index for all 50 Python scripts, including time complexity analysis for each using LaTeX notation.
   • All 10 categorical subdirectories now have a README.md file following a consistent ## Contents format with implementation-specific details and complexities.

3. Quality Assurance:

   • All 49 non-interactive Python scripts have been verified to execute successfully with Python 3.
   • A link verification script was run to ensure all relative links in Markdown files are valid following the refactor.
   • Standard GitHub slugging rules for Table of Contents anchor links were verified (emoji-stripping).

---

PR created automatically by Jules for task 15115155759508807075 started by @ppant

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.