vtorc: make SQL formatting consistent

[timvaillancourt]

Description

This PR improves the consistency of SQL statements in go/vt/vtorc (as discussed with @dbussink offline)

Some notes:

• Standardized on uppercase text for SQL verbs, functions, units, etc
  • Examples: SELECT, AS, OR, DATETIME, SECOND/HOUR/DAY, etc
• Standardized on \t for indentation - in places it's a mix of spaces and tabs
• Standardized when indentation happens, examples: list of columns/values, subqueries, conditions, etc
• Consistent spacing for value definitions, example something = ?
• Other minor style fixes

Related Issue(s)

#17164

Checklist

• "Backport to:" labels have been added if this change should be back-ported to release branches
• If this change is to be back-ported to previous releases, a justification is included in the PR description
• Tests were added or are not required
• Did the new or modified tests pass consistently locally and on CI?
• Documentation was added or is not required

Deployment Notes

[vitess-bot]

Review Checklist

Hello reviewers! 👋 Please follow this checklist when reviewing this Pull Request.

General

• Ensure that the Pull Request has a descriptive title.
• Ensure there is a link to an issue (except for internal cleanup and flaky test fixes), new features should have an RFC that documents use cases and test cases.

Tests

• Bug fixes should have at least one unit or end-to-end test, enhancement and new features should have a sufficient number of tests.

Documentation

• Apply the release notes (needs details) label if users need to know about this change.
• New features should be documented.
• There should be some code comments as to why things are implemented the way they are.
• There should be a comment at the top of each new or modified test to explain what the test does.

New flags

• Is this flag really necessary?
• Flag names must be clear and intuitive, use dashes (-), and have a clear help text.

If a workflow is added or modified:

• Each item in Jobs should be named in order to mark it as required.
• If the workflow needs to be marked as required, the maintainer team must be notified.

Backward compatibility

• Protobuf changes should be wire-compatible.
• Changes to _vt tables and RPCs need to be backward compatible.
• RPC changes should be compatible with vitess-operator
• If a flag is removed, then it should also be removed from vitess-operator and arewefastyet, if used there.
• vtctl command output order should be stable and awk-able.

[codecov]

Codecov Report

Attention: Patch coverage is 61.19403% with 130 lines in your changes missing coverage. Please review.

Project coverage is 67.44%. Comparing base (9ed8ee2) to head (29ae9d1).
Report is 8 commits behind head on main.

Files with missing lines	Patch %	Lines
go/vt/vtorc/logic/topology_recovery_dao.go	0.00%	81 Missing ⚠️
go/vt/vtorc/inst/instance_dao.go	85.51%	21 Missing ⚠️
go/vt/vtorc/logic/disable_recovery.go	0.00%	15 Missing ⚠️
go/vt/vtorc/process/health.go	0.00%	7 Missing ⚠️
go/vt/vtorc/inst/analysis_dao.go	84.84%	5 Missing ⚠️
go/vt/vtorc/logic/tablet_discovery.go	0.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #17154      +/-   ##
==========================================
- Coverage   67.44%   67.44%   -0.01%     
==========================================
  Files        1569     1569              
  Lines      252119   252165      +46     
==========================================
+ Hits       170038   170068      +30     
- Misses      82081    82097      +16     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.