ALTER query is executing too many things!

[abmmhasan]

Describe the bug
While doing an ALTER just will execute what it is given, instead it also doing too many other things.

To Reproduce
Steps to reproduce the behavior:

1. Go to 'Settings of any table'
2. Add a new column (as an ALTER example)
3. Check the console
4. See what it actually executed

Expected behavior
ALTER TABLE demo_db.customer_query_histories ADD COLUMN transaction_id VARCHAR(192) NULL AFTER contacted_for;

but it is running:
ALTER TABLE demo_db.customer_query_histories ADD COLUMN transaction_id VARCHAR(192) NULL AFTER contacted_for;ALTER TABLE demo_db.customer_query_histories CHANGE COLUMN id id BIGINT(20) UNSIGNED NOT NULL AUTO_INCREMENT FIRST, CHANGE COLUMN tracking_id tracking_id VARCHAR(30) NOT NULL COLLATE utf8mb4_general_ci AFTER id, CHANGE COLUMN customer_mobile_number customer_mobile_number VARCHAR(20) NOT NULL COLLATE utf8mb4_general_ci AFTER tracking_id, CHANGE COLUMN description description TEXT NULL COLLATE utf8mb4_general_ci AFTER customer_mobile_number, CHANGE COLUMN query_type query_type ENUM('self_onboard','transaction_status','agent_requested','other') NOT NULL COLLATE utf8mb4_general_ci DEFAULT 'other' AFTER description, CHANGE COLUMN source source ENUM('ivr','other') NOT NULL COLLATE utf8mb4_general_ci DEFAULT 'ivr' AFTER query_type, CHANGE COLUMN support_user_id support_user_id BIGINT(20) UNSIGNED NULL DEFAULT NULL AFTER source, CHANGE COLUMN contacted_for contacted_for VARCHAR(40) NULL COLLATE utf8mb4_general_ci DEFAULT NULL AFTER support_user_id, CHANGE COLUMN status status ENUM('new','responded','closed','auto_responded') NOT NULL COLLATE utf8mb4_general_ci DEFAULT 'new' AFTER transaction_id, CHANGE COLUMN call_status call_status ENUM('not_attempted','call_back_done','call_back_later','number_busy','did_not_pick','switched_off','not_interested_to_talk') NULL COLLATE utf8mb4_general_ci DEFAULT NULL AFTER status, CHANGE COLUMN schedule_at schedule_at DATETIME NULL DEFAULT NULL AFTER call_status, CHANGE COLUMN created_at created_at TIMESTAMP NULL DEFAULT CURRENT_TIMESTAMP AFTER schedule_at, CHANGE COLUMN updated_at updated_at TIMESTAMP NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP AFTER created_at

Screenshots
If applicable, add screenshots to help explain your problem.

Application (please complete the following information):

• Antares MySQL
• Latest from Snap
• Snap Store

Environment (please complete the following information):

• OS name: Ubuntu
• OS version 24.04
• DB name MYSQL
• DB version 8.0.37

Additional context
Add any other context about the problem here.