Refactor documentation structure and reduce redundancy

[HarunJr]

Restructured sessions into quarterly modules (Q1/Q2) and centralized shared operational guidelines.

Thank you for contributing to Developer Experience Working Group. Please fill out the following template, selecting the sections that best suit your case, to assist us in reviewing your PR.

Description

Summary

Restructures the Developer Experience Working Group documentation to split sessions into quarterly modules (Q1/Q2) and consolidates shared operational guidelines to a single source of truth.

Key Changes

• Session Restructure: Organized session content into dedicated quarterly modules for improved navigation.
• Sidebar: Configured sidebar categories to be collapsible and link directly to their respective overview plans.
• DRY Refactor: Centralized shared operational details (such as roles, delivery, and structure) into the main working group overview, removing redundant content from individual session plans.
• Cleanup:
  • Removed legacy directories and outdated assets.
  • Consolidated media resources and removed duplicate folders.
  • Updated structure diagrams and internal reference links.

Type of Change

Check the type of change this PR introduces:

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Refactor (improves code structure or readability without changing functionality)
• Other (please describe):

Changes Made

What changes were made to the codebase?
Include details about files modified, functions/logic modified.

Checklist

Ensure you have completed the following steps before submitting your PR:

• My code follows the project's coding style and guidelines.
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• I have updated the documentation (if applicable).
• My changes generate no new warnings or errors.
• I have added tests that prove my fix is effective or that my feature works.
• I have checked for merge conflicts.
• I have rebased my branch onto the latest main or master branch.