Support last_insert_id() with argument in SELECT

[systay]

Description

This PR adds support for LAST_INSERT_ID(expr) in Vitess. The feature allows the argument expr to be evaluated and stored as the session’s last insert ID, aligning with MySQL’s behavior. This extends Vitess’ compatibility for queries that rely on setting or retrieving session-level last insert ID values programmatically.

However, unlike MySQL, this feature is limited to usage within SELECT expressions only (i.e., it cannot be used in WHERE, GROUP BY, HAVING, or other non-SELECT contexts), which introduces a remaining compatibility gap.

Related Issue(s)

Work towards fixing #6087

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

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

Project coverage is 67.45%. Comparing base (ac23e59) to head (31af9e0).
Report is 11 commits behind head on main.

Files with missing lines	Patch %	Lines
go/vt/vtgate/engine/save_to_session.go	13.84%	56 Missing ⚠️
go/vt/sqlparser/copy_on_write.go	0.00%	20 Missing ⚠️
...vt/vtgate/planbuilder/operators/save_to_session.go	9.09%	20 Missing ⚠️
.../vt/vtgate/planbuilder/operators/query_planning.go	79.54%	9 Missing ⚠️
...o/vt/vtgate/planbuilder/single_sharded_shortcut.go	72.22%	5 Missing ⚠️
go/vt/vtgate/planbuilder/operator_transformers.go	83.33%	4 Missing ⚠️
go/vt/vtgate/executorcontext/vcursor_impl.go	0.00%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #17295      +/-   ##
==========================================
- Coverage   67.46%   67.45%   -0.02%     
==========================================
  Files        1581     1583       +2     
  Lines      253934   254132     +198     
==========================================
+ Hits       171329   171416      +87     
- Misses      82605    82716     +111     

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

[frouioui]

It would be good to link to the PR and/or Issue so there is more context for those wanting to learn more.

Suggested change

	### <a id="last_insert_id"/>Added support for LAST_INSERT_ID(expr)
	Added support for LAST_INSERT_ID(expr) to align with MySQL behavior, enabling session-level assignment of the last insert ID via query expressions.
	### <a id="last_insert_id"/>Added support for LAST_INSERT_ID(expr)
	Added support for `LAST_INSERT_ID(expr)` to align with MySQL behavior, enabling session-level assignment of the last insert ID via query expressions. For more information about this change see [#17295](https://github.com/vitessio/vitess/pull/17295).

[frouioui]

Suggested change

	Copyright 2019 The Vitess Authors.
	Copyright 2024 The Vitess Authors.

[frouioui]

just some minor comments, otherwise looks good to me, thank you! 🙇🏻

[systay]

Trying to get #17369 to cover all cases. Will close this for now