Refactor `apache/shardingsphere-elasticjob-ui` using Flutter to simultaneously implement functionality on both Android and web platforms

[linghengqian]

Feature Request

For English only, other languages will not accept.

Please pay attention on issues you submitted, because we maybe need more details.
If no response anymore and we cannot make decision by current information, we will close it.

Please answer these questions before submitting your issue. Thanks!

Is your feature request related to a problem?

• See elasticjob-ui is not compatible with the latest version (3.1.0-SNAPSHOT) #2448 .

Describe the feature you would like.

• Refactor apache/shardingsphere-elasticjob-ui using Flutter to simultaneously implement functionality on both Android and web platforms.
• For years, none of the maintainers of ShardingSphere have been active enough to know how to maintain a Vue project, resulting in https://github.com/apache/shardingsphere-elasticjob-ui being shelved for a long time. elasticjob-ui is not compatible with the latest version (3.1.0-SNAPSHOT) #2448 indicates that https://github.com/apache/shardingsphere-elasticjob-ui is no longer compatible with the main branch of https://github.com/apache/shardingsphere-elasticjob .
• I think fixing Refactor frontend with vue3, vite and typescript shardingsphere-elasticjob-ui#116 is an extremely painful process. Migrating from Vue2 to Vue3 is essentially rewriting the project, and it doesn't bring any benefits to the mobile experience. The only benefit is fixing the CVE. This was already evident during the painful review process of This pr is mainly used to upgrade the technology stack of the ui skywalking-banyandb#179.
• Personally, I prefer to reimplement apache/shardingsphere-elasticjob-ui and adopt Flutter, which is more widely used than the Vue ecosystem, to unify the technology stack used by our project at the front end. We still need a real backend project as the gateway for ShardingSphere-Elasticjob-UI to manage connections to ZooKeeper or etcd; this will definitely be a Docker image. The web-based ShardingSphere-Elasticjob-UI will continue to be packaged as a Docker image. The Android-based ShardingSphere-Elasticjob-UI will output an APK file for connecting to remote ShardingSphere-Elasticjob-UI gateway instances.

[linghengqian]

This is indeed a long-term project, but I will get started on it.

[linghengqian]

Authentication may not be a major issue. We can simply reuse the approach from https://casbin.apache.org/ , as ShardingSphere-Elasticjob-UI has historically relied on casbin for authorization.

We're unlikely to package the UI gateways into the Android client APK; the gateways will still need to be deployed separately via a Docker image.

Of course, I don't rule out the possibility of such a special approach.