feat: add mcp node

[BillorBear]

Summary

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation update
• Refactoring

Related Issue

Changes

Testing

• Existing tests pass
• New tests added (if applicable)
• Manual testing completed

Screenshots (if applicable)

Checklist

• Code follows project coding standards
• Self-review completed
• Documentation updated (if needed)
• Breaking changes documented

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[gemini-code-assist]

Code Review

This pull request introduces a new MCP workflow node. It modifies the database schema by adding an order_no column to config_info and config_info_en tables and inserts the new node configuration. My review identified a couple of issues in the SQL migration script: hardcoded schema names in ALTER TABLE statements, which can affect portability, and the inclusion of SELECT statements that seem to be for debugging and should be removed from a production migration script. I've provided suggestions to address these points.

[gemini-code-assist]

The schema name astron_console is hardcoded in the ALTER TABLE statements. This can cause issues in environments where a different schema name is used. It's better to rely on the schema configured for the Flyway connection and not hardcode it in migration scripts. Other migration scripts in this repository do not seem to hardcode the schema name.

ALTER TABLE config_info ADD order_no INT NULL;
ALTER TABLE config_info_en ADD order_no INT NULL;

[gemini-code-assist]

These SELECT statements appear to be for debugging purposes. They do not modify the database schema or data and should be removed from the migration script. Including them can create unnecessary log output and clutter during database migrations.