C# type safety when passing collections across the api surface

### Is there an existing issue for this?

- [X] I have searched the existing issues

### Suggestion

some objects require a collection in their constructor and take ownership of the collection, such as objects in manifest.cs. this ticket is to fix type safety issues across the dll/pinvoke native interface so that developers do not make transcription mistakes when modifying the library code.

### Possible Implementation

_No response_

### Anything else?

_No response_

首先检查 manifest.cs，并跟踪集合跨越 API 边界时所经过的原生 DLL/PInvoke 接口。识别 issue 中描述的集合所有权和类型安全性不匹配，然后定义所需的更改，使集合参数保持一致，并防止整个接口中出现转录错误。

由索引模型根据 Issue 内容生成。