Add GetTransactionInfo in VTadmin API and page

[GuptaManan100]

Description

This PR adds a VTAdmin API for getting the transaction information added in #17131. This PR should be merged after it is #17131.

This PR also adds a page to display the following page -

Related Issue(s)

• RFC: Atomic Distributed Transactions #16245
• Feature Request: Distributed Transaction Actions on VTAdmin  #16766

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 3.84615% with 25 lines in your changes missing coverage. Please review.

Project coverage is 67.32%. Comparing base (d9ab9f7) to head (6e3e999).
Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
go/vt/vtadmin/api.go	6.66%	14 Missing ⚠️
go/vt/vtadmin/http/transactions.go	0.00%	11 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #17142      +/-   ##
==========================================
- Coverage   67.33%   67.32%   -0.02%     
==========================================
  Files        1569     1569              
  Lines      252476   252502      +26     
==========================================
- Hits       170008   169996      -12     
- Misses      82468    82506      +38     

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

[harshit-gangal]

The screenshot above have invalid date is that because of the input data? Have you validated it with real data?

[notfelineit]

Left one comment!

[GuptaManan100]

Thank you for the reviews! I have fixed up all the comments and also the parsing of time. We were passing it in in nanoseconds, but the dayjs was expecting it to be in seconds. I have fixed this now.