chore: remove neo tables

[renancloudwalk]

No description provided.

[github-actions]

PR Review

⏱️ Estimated effort to review [1-5]	2, because the PR mainly involves the removal of large blocks of SQL code related to the 'neo' tables and their partitions. The changes are straightforward and mostly involve deletions, which are generally easier to review than additions or modifications of complex logic.
🧪 Relevant tests	No
🔍 Possible issues	Data Loss: Removing database tables and their associated partitions can lead to irreversible data loss if not properly backed up or if the removal is unintended. Ensure that this data is either backed up or truly no longer needed.
	Dependency Issues: If other parts of the application or database rely on the existence of these tables or their data, removing them could cause failures elsewhere. Verify that no dependencies exist before proceeding with this removal.
🔒 Security concerns	No

Code feedback:

---

✨ Review tool usage guide:

---

Overview:
The review tool scans the PR code changes, and generates a PR review which includes several types of feedbacks, such as possible PR issues, security threats and relevant test in the PR. More feedbacks can be added by configuring the tool.

The tool can be triggered automatically every time a new PR is opened, or can be invoked manually by commenting on any PR.

• When commenting, to edit configurations related to the review tool (pr_reviewer section), use the following template:

/review --pr_reviewer.some_config1=... --pr_reviewer.some_config2=...

• With a configuration file, use the following template:

[pr_reviewer]
some_config1=...
some_config2=...

See the review usage page for a comprehensive guide on using this tool.

[github-actions]

PR Code Suggestions

Category	Suggestions
Bug	Add a semicolon to the end of the SQL insert statement to ensure proper termination. Ensure that the INSERT INTO "schema_migrations" statement includes a semicolon at the end to prevent potential SQL execution errors. static/schema/001-init.sql [669] -INSERT INTO "schema_migrations" (version) VALUES +INSERT INTO "schema_migrations" (version) VALUES;

---

✨ Improve tool usage guide:

---

Overview:
The improve tool scans the PR code changes, and automatically generates suggestions for improving the PR code. The tool can be triggered automatically every time a new PR is opened, or can be invoked manually by commenting on a PR.

• When commenting, to edit configurations related to the improve tool (pr_code_suggestions section), use the following template:

/improve --pr_code_suggestions.some_config1=... --pr_code_suggestions.some_config2=...

• With a configuration file, use the following template:

[pr_code_suggestions]
some_config1=...
some_config2=...

See the improve usage page for a comprehensive guide on using this tool.