[MM-58341] db/migrations: mysql-8.4 fix for 000027_create_status

[isacikgoz]

Summary

MySQL v8.4 introduces a new reserved work for Manual hence it was causing errors during creating the new Status table. This issue was affecting new installations using mysql-8.4.

Ticket Link

https://mattermost.atlassian.net/browse/MM-58341

Release Note

NONE

[agnivade]

MySQL is dead. Long live MySQL.

[harshilsharma63]

While this fixes the migration, we also need to make the same change wherever we're querying this column in SQL store. For example, running this branch generates this error on opening webapp when the server tries to update user's status-

{
  "timestamp": "2024-05-23 09:04:18.344 +05:30",
  "level": "warn",
  "msg": "Failed to save status",
  "caller": "platform/status.go:288",
  "user_id": "ctgbai6zc3fyupk6zpynzdrsme",
  "error": "failed to upsert Status: Error 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'Manual,LastActivityAt,DNDEndTime,PrevStatus) VALUES (?,?,?,?,?,?) ON DUPLICATE K' at line 1"
}

So, we need to handle this in other places as well.

[agnivade]

Ah nice catch Harshil

[github-actions]

⚠️ One or more flaky tests detected ⚠️

• Failing job: github.com/mattermost/mattermost:Postgres with binary parameters
• Double check your code to ensure you haven't introduced a flaky test.
• If this seems to be unrelated to your changes, submit a separate pull request to skip the flaky tests (e.g. 23360) and file JIRA ticket (e.g. MM-52743) for later investigation.

[isacikgoz]

/update-branch