app-module events & callstack config, crash diagnostics (#630)

- Apps can specify task stack depth and preferred memory placement in their manifests.
- App identifiers are validated against length and character requirements.
- Crash diagnostics now show the crash cause, reason, fault address, call stack, and program-counter details, with logs saved for review.
- App closing is more consistent across built-in screens. There's now a dedicated function, and the old _emit() function is made private.
- Crash diagnostics no longer display a QR code without a call stack.
- Improved memory allocation for unrestricted requests.

Modules/app-module/source/app_install.cpp

@@ -4,8 +4,8 @@
 #include <app/manager.h>
 #include <app/metadata.h>
 
-#include <app/private/app_fs.h>
-#include <app/private/app_ledger.h>
+#include <app/private/fs.h>
+#include <app/private/ledger.h>
 
 #include <tactility/concurrent/mutex.h>
 #include <tactility/filesystem/file_mutex.h>
@@ -180,6 +180,7 @@ error_t register_installed_app_locked(const std::string& app_dir_path, const App
         .category = APP_CATEGORY_USER,
         .location = { APP_LOCATION_PATH, const_cast<char*>(record->path.c_str()) },
         .flags = 0,
+        .stack = { .depth = static_cast<uint16_t>(metadata.stack_depth), .desired_memory_capability = 0 },
     };
 
     // Belt-and-braces: app_install()'s earlier app_manager_remove() call is meant to have