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/editor.h

@@ -51,6 +51,7 @@ struct EditorContext {
 };
 
 enum class EditorType {
+  kUnknown,
   kAssembly,
   kDungeon,
   kEmulator,
@@ -66,7 +67,8 @@ enum class EditorType {
   kSettings,
 };
 
-constexpr std::array<const char*, 13> kEditorNames = {
+constexpr std::array<const char*, 14> kEditorNames = {
+    "Unknown",
     "Assembly", "Dungeon", "Emulator", "Graphics", "Music", "Overworld",
     "Palette",  "Screen",  "Sprite",   "Message",  "Hex",   "Agent", "Settings",
 };