Add filtering by metadata

[shefalijoshi]

Closes: #7389

Describe your changes:

Added a new filtering section for metadata filters
Added new sourceMap array property filterMetadata to specify a list of properties for metadata filtering.
Example:

"sourceMap": {
"filterMetadata": ["description", "properties.latitude"]
}

All Submissions:

• Have you followed the guidelines in our Contributing document?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?
• Is this change backwards compatible? For example, developers won't need to change how they are calling the API or how they've extended core plugins such as Tables or Plots.

Author Checklist

• Changes address original issue?
• Tests included and/or updated with changes?
• Has this been smoke tested?
• Have you associated this PR with a type: label? Note: this is not necessarily the same as the original issue.
• Have you associated a milestone with this PR? Note: leave blank if unsure.
• Is this a breaking change to be called out in the release notes?
• Testing instructions included in associated issue OR is this a dependency/testcase change?

Reviewer Checklist

• Changes appear to address issue?
• Reviewer has tested changes by following the provided instructions?
• Changes appear not to be breaking changes?
• Appropriate automated tests included?
• Code style and in-line documentation are appropriate?

[codecov]

Codecov Report

Attention: 31 lines in your changes are missing coverage. Please review.

Comparison is base (1fc6056) 55.90% compared to head (4b0ab1e) 55.91%.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #7388   +/-   ##
=======================================
  Coverage   55.90%   55.91%           
=======================================
  Files         662      662           
  Lines       26397    26432   +35     
  Branches     2563     2574   +11     
=======================================
+ Hits        14757    14779   +22     
- Misses      10928    10939   +11     
- Partials      712      714    +2     

Flag	Coverage Δ
e2e-full	41.87% <ø> (ø)
e2e-stable	59.78% <0.00%> (-0.04%)	⬇️
unit	48.94% <35.41%> (-0.01%)	⬇️

Files	Coverage Δ
src/plugins/timelist/plugin.js	100.00% <ø> (ø)
src/plugins/plan/util.js	45.76% <45.45%> (-0.08%)	⬇️
src/plugins/timelist/TimelistComponent.vue	59.72% <66.66%> (+3.90%)	⬆️
.../plugins/timelist/inspector/FilteringComponent.vue	0.00% <0.00%> (ø)

... and 3 files with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1fc6056...4b0ab1e. Read the comment docs.

[michaelrogers]

Invalid metadata filters can be saved for example foo.bar. Otherwise, these changes look good to me; filtering by metadata is working as expected.

[charlesh88]

Ran locally with a test plan with metadata and appears to work correctly. Added a "No filters applied" message for both input areas and additional detail about how it works in the hint text visible while editing. LGTM.

Test plan:
Synth plan 2024-01-25.json

[shefalijoshi]

Invalid metadata filters can be saved for example foo.bar. Otherwise, these changes look good to me; filtering by metadata is working as expected.

This is fixed now. Please re-test and review.

[michaelrogers]

Nice work! These changes look good to me. There is a linting error for an unused import in TimelistComponent.vue that will need to be addressed before merging.

There are some observations about the behavior of the filtering that might be worth noting that aren't necessarily bugs:

• If a user inputs an invalid string and saves, the string will be chopped off at the invalid character without informing the user (though it can be verified in the textarea after saving). If the invalid char is at the beginning like :foobar, then this term will not be saved at all. Otherwise if it is like foo.bar, only foo will be saved as a search term (which is probably okay).
• The properties metadata is only traversed at the first level. So a value in this field would not be searched properties.level1.level2.
• Adding only whitespace or a null value in the comma separated list will match all values. foo, ,bar or foo,,bar.