refactor(frontend): ignore stmts START TRANSACTION and ABORT

[likzn]

What's changed and what's your intention?

As issue #2595 say. We return them directly before the investigation of the behavior of pg .

Main changes:

1. Support parser to parse ABORT
2. src/frontend/src/handler/mod.rs#handler will return empty response when meet START TRANSACTION and ABORT

Checklist

• I have written necessary docs and comments
• I have added necessary unit tests and integration tests

Refer to a related PR or issue link (optional)

#2595

[neverchanje]

lgtm, Thanks for your contribution!

[likzn]

@neverchanje I find CI failed again in the same problem.So i update branch, but i find i cannot trigger CI. Maybe need you to trigger.

[neverchanje]

Sure, due to the limitation of our current CI service, I gonna fork your pr to our main branch, pls wait a minute:
https://github.com/singularity-data/risingwave/blob/main/CONTRIBUTING.md#to-check-in-prs-from-forks

[codecov]

Codecov Report

Merging #2607 (9c28e45) into main (f0d55a8) will decrease coverage by 0.01%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main    #2607      +/-   ##
==========================================
- Coverage   72.17%   72.16%   -0.02%     
==========================================
  Files         678      678              
  Lines       88260    88271      +11     
==========================================
- Hits        63701    63699       -2     
- Misses      24559    24572      +13     

Flag	Coverage Δ
rust	72.16% <0.00%> (-0.02%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
src/frontend/src/handler/mod.rs	46.91% <0.00%> (-5.15%)	⬇️
src/sqlparser/src/ast/mod.rs	88.23% <0.00%> (-0.21%)	⬇️
src/sqlparser/src/parser.rs	92.56% <0.00%> (-0.05%)	⬇️
src/utils/pgwire/src/pg_response.rs	35.08% <ø> (ø)
src/storage/src/object/disk.rs	95.45% <0.00%> (-0.27%)	⬇️
src/common/src/types/ordered_float.rs	24.70% <0.00%> (-0.20%)	⬇️

📣 Codecov can now indicate which changes are the most critical in Pull Requests. Learn more