Enhance prefab export and input handling features in editor

[amasiye]

This pull request updates the editor documentation to reflect several major usability improvements, new features, and workflow enhancements. The changes focus on expanding prefab support, improving hierarchy and inspector workflows, enhancing keyboard and mouse controls, and introducing a notification system. The documentation now more clearly describes how to use these new features and provides updated examples and configuration details.

Prefab and Hierarchy Workflow Enhancements:

• Added support for exporting hierarchy objects as reusable prefabs using Shift+E, with automatic file naming, selection, and inspector focus. Prefab files are written immediately and can be edited directly in the Inspector. [1] [2] [3] [4]
• Expanded hierarchy controls: Shift+D duplicates selected objects (with smart renaming), Ctrl+Click allows multi-selection, and Shift+W/Shift+Q enter and exit hierarchy move mode. Hierarchy rows now support expand/collapse and persistent expand state for nested branches. [1] [2] [3] [4] [5]

Inspector and Prefab Field Improvements:

• Inspector now treats GameObject fields as prefab references, with a modal picker for assignment and path resolution. Prefab assets open in object-editing mode, allowing immediate edits to fields and components. [1] [2] [3] [4] [5]

Input and Interaction Updates:

• Improved keyboard and mouse controls across panels: new shortcuts for prefab export, duplication, and move mode; mouse support for selection and activation in modals, hierarchy, assets, scene, and sprite panels; double-click to activate controls. [1] [2] [3] [4] [5] [6] [7] [8]

Console and Notification System:

• Console panel now supports filtering, clearing, and starts the Debug tab on the DEBUG filter. Added a top-right snackbar for transient notifications (success, error, info, warn), with configurable duration. [1] [2] [3] [4] [5]

Documentation and Configuration Updates:

• Updated all relevant guides and configuration examples to reference new features (e.g., preferences.json instead of configuration.json, notification settings, prefab workflows), and clarified editor expectations and project structure. [1] [2] [3]

These updates collectively make the editor more powerful and user-friendly, especially for workflows involving prefabs, complex hierarchies, and rapid asset iteration.