[EPIC] Support Hbase catalog

### Describe the proposal

[Apache](https://www.apache.org/) [HBase®](https://hbase.apache.org/) is the [Hadoop](https://hadoop.apache.org/) database, a distributed, scalable, big data store.
Use Apache HBase® when you need random, realtime read/write access to your Big Data. This project's goal is the hosting of very large tables -- billions of rows X millions of columns -- atop clusters of commodity hardware. Apache HBase® is an open-source, distributed, versioned, non-relational database modeled after Google's [Bigtable: A Distributed Storage System for Structured Data](https://research.google.com/archive/bigtable.html) by Chang et al. Just as Bigtable leverages the distributed data storage provided by the Google File System, Apache HBase® provides Bigtable-like capabilities on top of Hadoop and HDFS .

Gravitino currently supports[ MySQL](https://www.mysql.com/) ,[ PostgreSQL](https://www.postgresql.org/) and[ Apache Doris](https://doris.apache.org/) metadata management but does not support Phoenix yet. This proposal is to add Phoenix JDBC catalog support in Gravitino so that users can have more options for managing database metadata.

### Task list

- [ ] https://github.com/apache/gravitino/issues/6020 @flaming-archer

Start with the linked task, issue #6020, and review how Gravitino currently supports MySQL, PostgreSQL, and Apache Doris metadata catalogs. The proposal's stated completion goal is adding Apache Phoenix JDBC catalog support; the issue does not name implementation files or tests.

Written by the indexing model from the issue text.