fix: 【发行为混合分包】TypeError: t.$callHook is not a function

[viccici]

#4781

1. 当发行为混合分包的时候，uniapp 会调用 initCreateSubpackageApp 方法

2. initCreateSubpackageApp 里调用 parseApp ，并在 onLaunch 时候进行 initBaseInstance

3. initCreateSubpackageApp 里调用 parseApp 后同步执行 vm.$.ctx.$scope = app;

4. initBaseInstance 在 onLaunch 会进行 if (this.$vm && ctx.$scope) {return;} 阻断，如果通过则执行 ctx.$hasHook = hasHook; ctx.$callHook = callHook;

问题出在 onLaunch 是异步的，导致 4 的流程阻断，没有执行 $callHook 赋值，最终导致 initAppLifecycle 中的 vm.$callHook 为 undefined

[Copilot]

Pull Request Overview

This PR fixes a race condition that resulted in a TypeError when using mixed subpackages in uniapp by synchronously assigning hook functions to the application context.

• Synchronously assigns $hasHook and $callHook to resolve the asynchronous initialization issue.
• Ensures hooks are available before onLaunch completes.

[Copilot]

Assigning '$hasHook' and '$callHook' synchronously resolves the async race condition that previously resulted in 't.$callHook is not a function'. Consider adding a comment explaining why these assignments are done here for future maintainability.

Suggested change

	;(vm.$ as any).ctx.$scope = app
	;(vm.$ as any).ctx.$scope = app
	// Assigning `$hasHook` and `$callHook` synchronously is critical to prevent
	// an async race condition that could result in `t.$callHook is not a function`.
	// Do not modify the order or timing of these assignments without understanding
	// the potential impact on app lifecycle hooks.