Implement state:modified for saved queries

[gshank]

resolves #10294

Problem

Doing state:modified for saved queries didn't work.

Solution

Implement state:modified for saved queries.

Checklist

• I have read the contributing guide and understand what's expected of me
• I have run this code in development and it appears to resolve the stated issue
• This PR includes tests, or tests are not required/relevant for this PR
• This PR has no interface changes (e.g. macros, cli, logs, json artifacts, config files, adapter interface, etc) or this PR has already received feedback and approval from Product or DX
• This PR includes type annotations for new and modified functions

[github-actions]

Thank you for your pull request! We could not find a changelog entry for this change. For details on how to document a change, see the contributing guide.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.78%. Comparing base (c5be8e2) to head (c915283).
Report is 9 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #10295      +/-   ##
==========================================
+ Coverage   88.72%   88.78%   +0.05%     
==========================================
  Files         180      180              
  Lines       22497    22490       -7     
==========================================
+ Hits        19961    19967       +6     
+ Misses       2536     2523      -13     

Flag	Coverage Δ
integration	86.04% <100.00%> (+0.05%)	⬆️
unit	62.19% <100.00%> (+0.45%)	⬆️

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.

[QMalcolm]

This looks great! Thank you for fixing it 🙂

[ChenyuLInx]

LGTM!
Two things that are not blocker:

• is it possible to unit test this change?
• should we consider move this select modified test to the test for list command and use the new happy path fixture to test it? You can create a follow up ticket and give it to me.

Oh and another thing is if we want to list modified semantic model and metrics, do we need to do similar change? CC @aliceliu since she is working on something related

[gshank]

I think that semantic_models and metrics are already listable. What is Alice working on?

[gshank]

@ChenyuLInx I'll add some unit tests. As far as a functional test, it's really a selection thing, not precisely list (though they certainly overlap). Will look at what gets into the happy path tests...