Configurable hook execution order for extensions

Summary Allow explicit control over the execution order of custom hooks/extensions listening to the same event in Directus. Basic Example Suppose you have two hooks: one called hook-virus-scanner that scans uploaded files for viruses, and another called hook-file-processor that processes files after upload. With this feature, you could explicitly specify that hook-virus-scanner should always run before hook-file-processor, ensuring files are scanned before any processing occurs. Motivation Currently, the execution order of hooks is determined by their names, which is not explicit or reliable. This limits modularity and maintainability, as developers must use naming conventions to control order. Explicit ordering would enable smaller, focused extensions and allow instance-level customization, supporting more complex and modular workflows. Detailed Design • Introduce an order property for hook definitions, or a global configuration mapping events to hook execu…