[FEATURE] Support FlinkSQL on Kubernetes

### Code of Conduct

- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)

### Search before asking

- [X] I have searched in the [issues](https://github.com/apache/kyuubi/issues?q=is%3Aissue) and found no similar issues.

### Describe the feature

Kyuubi extends its capabilities to support FlinkSQL workloads on Kubernetes, empowering users to seamlessly deploy, manage, and execute FlinkSQL queries in a scalable and distributed cloud-native environment. With Kubernetes' dynamic resource allocation and orchestration, FlinkSQL jobs can take advantage of automated scaling, high availability, and optimized resource utilization. This integration simplifies running SQL analytics over streaming and batch data with Apache Flink, providing a unified interface for big data processing on Kubernetes clusters.

Key features include:

- Efficient job scheduling and management of FlinkSQL queries on K8s.
- Seamless integration with Kubernetes’ native resource management and auto-scaling.
- Support for both streaming and batch processing with SQL semantics.

### Motivation

_No response_

### Describe the solution

_No response_

### Additional context

_No response_

### Are you willing to submit PR?

- [ ] Yes. I would be willing to submit a PR with guidance from the Kyuubi community to improve.
- [X] No. I cannot submit a PR at this time.

The issue names no files, tests, or entry points. Begin by surveying Kyuubi’s current Kubernetes and SQL support, then clarify the intended FlinkSQL deployment, management, and execution scope; done criteria should cover the listed scheduling, resource-management, streaming, and batch capabilities.

Written by the indexing model from the issue text.