[Bug]: SIGSEGV(SEGV_ACCERR) Android初始化engine报错

### 请描述遇到的问题，以及您所期望的正确的结果

在activity页面initFlutterBoost，掉用 new FlutterEngine(application, options.shellArgs())方法

### 请说明如何操作会遇到上述问题

_No response_

### 在下面填入关键复现代码

```
```
#00 pc 0000007f0ee51368
2
#01 pc 0000007f0ee5126c
3
java:
4
io.flutter.embedding.engine.FlutterJNI.performNativeAttach(FlutterJNI.java:395)
5
io.flutter.embedding.engine.FlutterJNI.attachToNative(FlutterJNI.java:387)
6
io.flutter.embedding.engine.FlutterEngine.attachToJni(FlutterEngine.java:361)
7
io.flutter.embedding.engine.FlutterEngine.(FlutterEngine.java:339)
8
io.flutter.embedding.engine.FlutterEngine.(FlutterEngine.java:263)
9
io.flutter.embedding.engine.FlutterEngine.(FlutterEngine.java:243)
10
io.flutter.embedding.engine.FlutterEngine.(FlutterEngine.java:163)
11
com.idlefish.flutterboost.FlutterBoost.initEngine(FlutterBoost.java:84)

### 复现的平台

Android

### Flutter SDK版本

3.0.0

### FlutterBoost版本

4.3

### 是否延迟初始化FlutterBoost

Yes

### 解决方案

Start at FlutterBoost.java:84, where initEngine creates FlutterEngine, then inspect the FlutterEngine.attachToJni and FlutterJNI.performNativeAttach frames in the Android stack trace. Reproduce delayed initialization with Flutter SDK 3.0.0 and FlutterBoost 4.3; done means the SIGSEGV is explained and Android engine initialization no longer crashes, with a regression test or clear reproduction notes.

Written by the indexing model from the issue text.