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.

Tactility/Source/app/inputdialog/InputDialog.cpp

@@ -59,10 +59,7 @@ void onButtonPressed(lv_event_t* e) {
         LOG_I(TAG, "Cancel pressed");
         btnCtx->ctx->result = 1;
     }
-    // Async, non-blocking - see AlertDialog.cpp's onButtonPressed() for why this must not
-    // call app_manager_stop() directly (would deadlock against the LVGL lock).
-    AppEvent event { .type = APP_EVENT_CLOSE, .timestamp = 0, .result = {} };
-    app_event_emit(btnCtx->ctx->appInstanceId, &event);
+    app_event_emit_close(btnCtx->ctx->appInstanceId);
 }
 
 void createButton(Context* ctx, lv_obj_t* parent, const std::string& text, lv_obj_t* textarea) {