What problem does this PR solve?

Issue Number: close #57482

Problem Summary:

What changed and how does it work?

Add create/drop/set bindings to CRUCIAL OPERATION log.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)

• create a cluster
• run create/drop/set binding statements
• check CRUCIAL OPERATION log, e.g.

[2024/11/19 11:19:54.383 +08:00] [INFO] [session.go:4109] ["CRUCIAL OPERATION"] [conn=2097154] [schemaVersion=55] [cur_db=test] [sql="create global binding using select 1"] [user=root@%]
[2024/11/19 11:21:19.221 +08:00] [INFO] [session.go:4109] ["CRUCIAL OPERATION"] [conn=2097154] [schemaVersion=55] [cur_db=test] [sql="set binding disabled for select 1"] [user=root@%]
[2024/11/19 11:22:18.493 +08:00] [INFO] [session.go:4109] ["CRUCIAL OPERATION"] [conn=2097154] [schemaVersion=55] [cur_db=test] [sql="drop global binding for select 1"] [user=root@%]

• No need to test

  • I checked and no code files have been changed.

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None