Rewrite Manager using Miuix

[superturtlee]

A new manager GUI based on the miuix project has been added.
All features have been implemented except for the module repository and online update checks.
Since the module repository uses the Lsposed repository, the repository functionality has been removed to ensure the unique branding of the new Vector project. (I dont like LSPosed)
Online update checking overlaps with the KernelSU module update functionality, so it has been removed.

[JingMatrix]

@superturtlee Can you present some screenshots of your design ?

[superturtlee]

[superturtlee]

[HSSkyBoy]

我必須明確反對這次的設計：
這種介面完全照搬了澎湃的設計語言，對非澎湃系統使用者來說，是徹頭徹尾的「體驗災難」。
通用開源專案的UI設計，本應遵循自己的規範，而不是繫結單一廠商的系統標準。你這不是「風格參考」，是直接把別家的 UI 邏輯、互動正規化全抄過來，既不尊重其他系統使用者的使用習慣，也違背了開源專案的中立性。
以前我覺得 miuix 作為一個 UI 庫，功能上沒什麼問題，但你這種完全是介面風格的同質化抄襲，已經不是借鑒的範疇了，完全忽略了其它系統使用者的使用體驗。

I strongly oppose this PR:
This interface is a blatant copy of HyperOS design language, resulting in a terrible experience for non-HyperOS users.
An open-source project should adhere to its own standards, not tie itself to a single vendor’s system. This is not “stylistic reference” — it is plagiarism of another product’s UI logic and interaction patterns, disrespecting other users and betraying open-source neutrality.
While  miuix  as a UI library was functionally acceptable, this homogeneous interface copy goes far beyond reasonable reference and completely ignores cross-platform user experience

[HSSkyBoy]

而且這就是一個完全的 Author by AI 的提交

[superturtlee]

而且這就是一個完全的 Author by AI 的提交

没办法，库里面的ui资源是这么写的
而且ai ui设计能力极差（我试过，都是错位+bug，完全不可用）
这个ui框架里面ui资源只有这些
实际上很多ui代码来源于hyperceiler（这可能是ui同质化原因之一，毕竟这软件像MIUI）
目前正在解耦ui和实际逻辑，简化ui代码

AI完成部分：Tab补全/写注释

the library do not have other designs

[JingMatrix]

@superturtlee

There is a new UI working in the branch https://github.com/JingMatrix/Vector/tree/refactor, I'd suggest that we work in this branch.
It is very primitive, and I will write a special design of the homepage.

However, I do need help to accelerate the development of other pages.

[superturtlee]

there are som

我必須明確反對這次的設計： 這種介面完全照搬了澎湃的設計語言，對非澎湃系統使用者來說，是徹頭徹尾的「體驗災難」。 通用開源專案的UI設計，本應遵循自己的規範，而不是繫結單一廠商的系統標準。你這不是「風格參考」，是直接把別家的 UI 邏輯、互動正規化全抄過來，既不尊重其他系統使用者的使用習慣，也違背了開源專案的中立性。 以前我覺得 miuix 作為一個 UI 庫，功能上沒什麼問題，但你這種完全是介面風格的同質化抄襲，已經不是借鑒的範疇了，完全忽略了其它系統使用者的使用體驗。

I strongly oppose this PR: This interface is a blatant copy of HyperOS design language, resulting in a terrible experience for non-HyperOS users. An open-source project should adhere to its own standards, not tie itself to a single vendor’s system. This is not “stylistic reference” — it is plagiarism of another product’s UI logic and interaction patterns, disrespecting other users and betraying open-source neutrality. While miuix as a UI library was functionally acceptable, this homogeneous interface copy goes far beyond reasonable reference and completely ignores cross-platform user experience

so why does it is called "miuix"

however I decoupled the UI design from the underlying logic. a MD3 version is in process

[JingMatrix]

@superturtlee For mainteance considering, we have to migrate to Compose API from current View system.

Hence, I suggest that you check the refactor branch, and we can work together for the new UI design.