[Feature][Connector] Add connectors for these datasources

Based on analysis of market popularity, the following 9 database/storage connectors are suggested to be supported in SeaTunnel.

### Database/Storage Connectors Tracking

| Type | Connector | Contributer | Status | PR |
| :--- | :--- | :--- | :--- | :--- |
| Source/Sink | Azure Cosmos DB | @SalvadorN323 (Sink) | Partial | |
| Source/Sink | CockroachDB | @sug-ghosh | Claimed | |
| Source/Sink | Amazon DocumentDB | | Todo | |
| Source/Sink | Firebase (Realtime Database) | | Todo | |
| Source | Couchbase | | Todo | |
| Sink | Couchbase | @srijan-singh | Doing | #11198 |
| Source/Sink | Sybase | | Todo | |
| Source/Sink | Ingres | | Todo | |
| Source/Sink | SingleStore (MemSQL) | @852511489 | Doing | #10521 |
| Source/Sink | Airtable | @kuleat | Done | #10469 |

### Context & Details

1. **Azure Cosmos DB**: Highly popular cloud-native database on Azure (NoSQL / Multi-model).
2. **CockroachDB**: Distributed SQL. Compatible with PostgreSQL wire protocol but dedicated connector allows optimized features.
3. **Amazon DocumentDB**: AWS managed document database (MongoDB-compatible).
4. **Firebase (Realtime Database)**: distinct from the existing `google-firestore` connector.
5. **Couchbase**: Enterprise-grade NoSQL document store.
6. **Sybase**: Legacy RDBMS widely used in financial sectors.
7. **Ingres**: Heritage relational database system.
8. **SingleStore (formerly MemSQL)**: High-performance real-time analytics database (HTAP).
9. **Airtable**: Low-code Database / Spreadsheet, popular as a data source.

Supplementary Note:
If you‘d like to implement either the source or sink of a datasource, please specify this clearly when leaving a message.

Start with the Database/Storage Connectors Tracking table and identify an unclaimed datasource and whether the contribution is a source or sink. Review the project’s connector contribution conventions before choosing scope; done means the selected connector is implemented and its status is updated with the relevant pull request.

Written by the indexing model from the issue text.