feat: Introduce Debugging and Testing Guide with enhanced startup options

- Added a new document, E5-debugging-guide.md, providing comprehensive strategies for debugging and testing the `yaze` application, including logging practices and testing frameworks.
- Updated E2-development-guide.md to include a new section on debugging and testing, detailing quick debugging methods using command-line flags for specific editors and UI cards.
- Enhanced the main application to support command-line flags for opening specific editors and cards on startup, improving the developer experience.
- Refactored the Controller class to handle startup editor and card initialization based on command-line inputs.

src/app/editor/graphics/graphics_editor.cc

@@ -85,8 +85,6 @@ void GraphicsEditor::Initialize() {
       .visibility_flag = &show_prototype_viewer_,
       .priority = 40
   });
-  
-  printf("[GraphicsEditor] Registered 4 cards with EditorCardManager\n");
 }
 
 absl::Status GraphicsEditor::Load() { 

src/app/editor/graphics/palette_editor.cc

@@ -187,9 +187,6 @@ absl::Status DisplayPalette(gfx::SnesPalette& palette, bool loaded) {
 }
 
 void PaletteEditor::Initialize() {
-  // PaletteEditor uses tabs within a single window, not separate cards
-  // So we don't register individual cards - the whole editor is one unit
-  printf("[PaletteEditor] No cards to register (uses internal tabs)\n");
 }
 
 absl::Status PaletteEditor::Load() {

src/app/editor/graphics/screen_editor.cc

@@ -82,8 +82,6 @@ void ScreenEditor::Initialize() {
       .visibility_flag = &show_naming_screen_,
       .priority = 50
   });
-  
-  printf("[ScreenEditor] Registered 5 cards with EditorCardManager\n");
 }
 
 absl::Status ScreenEditor::Load() {