Repository: georgia-tech-db/evadb (language: python)

Issue:
`test/third_party_tests` are not running on staging branch
### Search before asking

- [X] I have searched the EvaDB [issues](https://github.com/georgia-tech-db/eva/issues) and found no similar bug report.


### Bug

Currently, we have Mysql and PostgreSQL setup on the staging branch and their third_party_tests are running on the staging branch.

However, other tests (e.g., test/third_party_tests/test_github_datasource.py, test/third_party_tests/test_native_similarity_index.py) seem to be not running on the staging now. Some of them do not need special set up, and can run with long integration tests. 

@jiashenC which is the best way to handle this? Shall we move those tests that do not need special setup out of the third_party_tests or add a special mark to tests in third_party_tests that need special setup and include the directory in the long integration.

### Environment

_No response_

### Are you willing to submit a PR?

- [ ] Yes I'd like to help by submitting a PR!


Discussion / hints:
I see. Does `test/third_party_tests/test_github_datasource.py` require special setup? If not, we can move them out. The native similarity search test needs a special setup that Postgres's vector extension needs to be enabled. 
Get it. No it does not require special setup. I will move it outside `third_party_tests`. Does the native similarity search test run any where now? I think the postgres third party test also does not run the test. 

Fix patch:
diff --git a/docs/source/reference/databases/github.rst b/docs/source/reference/databases/github.rst
index 6674e6575f..00e706d49a 100644
--- a/docs/source/reference/databases/github.rst
+++ b/docs/source/reference/databases/github.rst
@@ -34,7 +34,7 @@ Create Connection
 Supported Tables
 ----------------
 
-* ``stargazers``: Lists the people that have starred the repository. Check `evadb/third_party/databases/github/table_column_info.py` for all the available columns in the table.
+* ``stargazers``: Lists the people that have starred the repository. Check `table_column_info.py <https://github.com/georgia-tech-db/evadb/blob/staging/evadb/third_party/databases/github/table_column_info.py>`_ for all the available columns in the table.
 
 .. code-block:: sql
 
@@ -54,4 +54,4 @@ Here is the query output:
 
 .. note::
 
-   Looking for another table from Github? You can add a table mapping in `evadb/third_party/databases/github/github_handler.py`, or simply raise a `Feature Request <https://github.com/georgia-tech-db/evadb/issues/new/choose>`_.
+   Looking for another table from Github? You can add a table mapping in `github_handler.py <https://github.com/georgia-tech-db/evadb/blob/staging/evadb/third_party/databases/github/github_handler.py>`_, or simply raise a `Feature Request <https://github.com/georgia-tech-db/evadb/issues/new/choose>`_.
diff --git a/evadb.db b/evadb.db
deleted file mode 100644
index e69de29bb2..0000000000


Test patch:
diff --git a/test/integration_tests/long/interfaces/relational/test_relational_api.py b/test/integration_tests/long/interfaces/relational/test_relational_api.py
index 773607960b..fee4029e2a 100644
--- a/test/integration_tests/long/interfaces/relational/test_relational_api.py
+++ b/test/integration_tests/long/interfaces/relational/test_relational_api.py
@@ -57,6 +57,7 @@ def tearDown(self):
         # todo: move these to relational apis as well
         execute_query_fetch_all(self.evadb, """DROP TABLE IF EXISTS mnist_video;""")
         execute_query_fetch_all(self.evadb, """DROP TABLE IF EXISTS meme_images;""")
+        execute_query_fetch_all(self.evadb, """DROP TABLE IF EXISTS dummy_table;""")
 
     def test_relation_apis(self):
         cursor = self.conn.cursor()
diff --git a/test/third_party_tests/test_github_datasource.py b/test/integration_tests/long/test_github_datasource.py
similarity index 100%
rename from test/third_party_tests/test_github_datasource.py
rename to test/integration_tests/long/test_github_datasource.py