Query to read transaction state

[GuptaManan100]

Description

This PR adds a query that can be used to read the transaction state of an ongoing 2PC transaction.
Syntax:
show transaction status for <dtid>

> show transaction status for <dtid>;
+-------------+---------+-------------------------------+-------------------+
| id          | state   | record_time                   | participants      |
+-------------+---------+-------------------------------+-------------------+
| ks:-80:4334 | PREPARE | 2024-07-06 04:05:34 +0000 UTC | ks:80-a0,ks:a0-c0 |
+-------------+---------+-------------------------------+-------------------+
1 row in set (0.00 sec)

If the transaction ID is does not exists or already resolved, empty result set will be returned.

Related Issue(s)

• RFC: Atomic Distributed Transactions #16245

Checklist

• 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

[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.25000% with 31 lines in your changes missing coverage. Please review.

Project coverage is 68.66%. Comparing base (ae7214d) to head (6ef7992).

Files	Patch %	Lines
go/vt/vtgate/engine/transaction_status.go	71.69%	15 Missing ⚠️
go/vt/vtgate/tx_conn.go	45.45%	6 Missing ⚠️
go/vt/sqlparser/ast.go	0.00%	4 Missing ⚠️
go/vt/sqlparser/ast_format.go	0.00%	2 Missing ⚠️
go/vt/vtgate/executor.go	0.00%	2 Missing ⚠️
go/vt/vtgate/vcursor_impl.go	0.00%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #16431      +/-   ##
==========================================
+ Coverage   68.64%   68.66%   +0.02%     
==========================================
  Files        1549     1550       +1     
  Lines      199214   199285      +71     
==========================================
+ Hits       136750   136844      +94     
+ Misses      62464    62441      -23     

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