[Discover] Query Editor Shortcut Fires Incorrect Query

[sejli]

Description

• When using keyboard shortcuts to run a query in Discover 2.0, the date range gets reverted to Discover's last date range state. Since there is no date range passed into the onSubmit() function from the editor shortcut, the QueryEditorTopRow uses the props passed from the search bar as dates, which may be out of sync compared to the query service state. This PR passes in the correct date form the query service.
• Additionally, in the multiline editor, the query object was being used to construct the new query. This PR updates it to match the single line editor, which uses the queryRef defined in the same file.

Issues Resolved

Screenshot

Testing the changes

Changelog

-fix: Fix Discover query editor enter shortcuts reverting date range

Check List

• All tests pass
  • yarn test:jest
  • yarn test:jest_integration
• New functionality includes testing.
• New functionality has been documented.
• Update CHANGELOG.md
• Commits are signed per the DCO using --signoff

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 3 lines in your changes missing coverage. Please review.

Project coverage is 61.68%. Comparing base (49f42c4) to head (b765af2).
Report is 9 commits behind head on main.

Files with missing lines	Patch %	Lines
...ugins/data/public/ui/query_editor/query_editor.tsx	0.00%	3 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #9248      +/-   ##
==========================================
- Coverage   61.69%   61.68%   -0.02%     
==========================================
  Files        3816     3816              
  Lines       91693    91694       +1     
  Branches    14516    14516              
==========================================
- Hits        56569    56559      -10     
- Misses      31498    31510      +12     
+ Partials     3626     3625       -1     

Flag	Coverage Δ
Linux_1	29.04% <ø> (ø)
Linux_2	56.46% <ø> (ø)
Linux_3	39.09% <0.00%> (+<0.01%)	⬆️
Linux_4	28.97% <ø> (ø)
Windows_1	29.06% <ø> (-0.02%)	⬇️
Windows_2	56.41% <ø> (ø)
Windows_3	39.09% <0.00%> (-0.01%)	⬇️
Windows_4	28.97% <ø> (ø)

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

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

[kavilla]

did we want to get this into 2.19?

[paulstn]

Regarding this change, I see that earlier in the file, queryRef exists for monaco 'commands' to access the latest query state.
If query was a stale query state, why wasn't the single line editor failing a test that would update the query?
If there is a test for an updated query state, and query has the updated query state, do we need queryRef at all? It only seems to be used here.