Persist container filter via settings

[pdjohntony]

The new filtering feature courtesy of @FilipCondac is great, seriously, I've wanted this for a long time.

It would be nice if filters could be defined as a settings so they can be applied at the workspace level and persist across sessions.

[FilipCondac]

Glad to hear more people are using this feature.

I understand the use case as you might have some lingering containers that you don't want to see across all workspace instances. I would be more than happy to implement this extension if @bwateratmsft thinks this is something that the project could use.

[bwateratmsft]

I like this idea! I'm thinking about what would be the best user experience...I'm leaning toward storing the filter value in the workspace memento, so it would persist for that workspace but would not be checked in to the settings.json file. I'm a little reluctant to add a new setting just for this--could get cluttery fast.

What do you think @pdjohntony --would it be sufficient if it persisted in a workspace (but could be changed at any time, of course), but did not exist as an explicit setting?

[pdjohntony]

While I could see an argument for a setting, I do think the workspace memento route is a better idea.