Separate components that ship separately into their own repos

[dblock]

Is your feature request related to a problem?

Coming from opensearch-project/opensearch-build#2188, it's not possible to release and tag the multiple components (workbench, sql-odbc, sql-jdbc, ...) that come out of this repo separately as, for example, 2.0.0. This means we must release all these parts together, or nobody can ever locate the correct code using tags.

What solution would you like?
The plugins/drivers should live in their own repos.

What alternatives have you considered?
A tagging scheme such as opensearch-2.0.0 vs. opensearch-odbc-driver-2.0.0.

[dblock]

See opensearch-project/opensearch-build#2188 (comment) in which we decided to split front-end and back-end components. For the SQL plugin there are a lot more individual components. Those that ship separately should split, and those that ship at the same time as the SQL plugin, can stay. @anirudha what do you think we should keep/split?

[dai-chen]

@YANG-DB I assume you've worked on this. Please close this once done. Thanks!

[dai-chen]

• Split JDBC Driver into it's own repository  #964
• Split ODBC Driver into it's own repository #965
• Split CLI Tool into it's own repository #966

[YANG-DB]

New Repos generated from internal folder in SQL :

• jdbc-sql ==> https://github.com/opensearch-project/sql-jdbc
• odbc-sql ==> https://github.com/opensearch-project/sql-odbc
• cli-sql ==> https://github.com/opensearch-project/sql-cli
• dashboards-query-workbench ==> https://github.com/opensearch-project/dashboards-query-workbench

Main SQL repo remains the plugin container with focus on SQL / PPL engine