evalEngine: Implement TIME_TO_SEC

[beingnoble03]

Description

This PR adds implementation of TIME_TO_SEC func in evalengine.

Related Issue(s)

Fixes part of #9647

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: 18 lines in your changes are missing coverage. Please review.

Comparison is base (77dc0c9) 47.70% compared to head (378ec2a) 47.79%.
Report is 12 commits behind head on main.

Files	Patch %	Lines
go/vt/vtgate/evalengine/cached_size.go	0.00%	10 Missing ⚠️
go/vt/vtgate/evalengine/fn_time.go	89.28%	2 Missing and 1 partial ⚠️
go/vt/vtgate/evalengine/translate_builtin.go	40.00%	2 Missing and 1 partial ⚠️
go/mysql/datetime/datetime.go	0.00%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #15094      +/-   ##
==========================================
+ Coverage   47.70%   47.79%   +0.09%     
==========================================
  Files        1155     1155              
  Lines      240218   240418     +200     
==========================================
+ Hits       114593   114906     +313     
+ Misses     117020   116940      -80     
+ Partials     8605     8572      -33     

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

[vmg]

This logic is duplicated in the evaluation VM too. Could you please extract it into a ToSeconds() method in Time?

[beingnoble03]

done.

[beingnoble03]

@vmg can you please review?

[vmg]

Thank you!