Dynamo Packages Host filters

[QilongTang]

Please Note:

1. Before submitting the PR, please review How to Contribute to Dynamo
2. Dynamo Team will meet 1x a month to review PRs found on Github (Issues will be handled separately)
3. PRs will be reviewed from oldest to newest
4. If a reviewed PR requires changes by the owner, the owner of the PR has 30 days to respond. If the PR has seen no activity by the next session, it will be either closed by the team or depending on its utility will be taken over by someone on the team
5. PRs should use either Dynamo's default PR template or one of these other template options in order to be considered for review.
6. PRs that do not have one of the Dynamo PR templates completely filled out with all declarations satisfied will not be reviewed by the Dynamo team.
7. PRs made to the DynamoRevit repo will need to be cherry-picked into all the DynamoRevit Release branches that Dynamo supports. Contributors will be responsible for cherry-picking their reviewed commits to the other branches after a LGTM label is added to the PR.

Purpose

This PR adds a host filter right next to the traditional package sorting option. I will look at illustrating the host dependencies on each package entry as well but the mock up data is not working for me. Regardless of that, the filter and package filtering code is done. Currently it is a global setting which will affect searched results and sorted results or any combination.

Declarations

Check these if you believe they are true

• The code base is in a better state after this PR
• Is documented according to the standards
• The level of testing this PR includes is appropriate
• User facing strings, if any, are extracted into *.resx files
• All tests pass using the self-service CI.
• Snapshot of UI changes, if any.
• Changes to the API follow Semantic Versioning, and are documented in the API Changes document.

Reviewers

@DynamoDS/dynamo

FYIs

@gregmarr

[QilongTang]

Not sure why the AppVeyor build failed, the following code should build fine but throwing errors on that VM.

        public List<FilterEntry> HostFilter
        {
            get => hostFilter;
            set
            {
                hostFilter = value;
                RaisePropertyChanged("HostFilter");
            }
        }

[QilongTang]

It turns out the code above is in a newer .Net comes with VS 2019 which our build vm does not support yet, so I updated to use the traditional way.

[mjkkirschner]

@QilongTang if you want to use that you'll need to swtich to using msbuild 15 I think on the build machine. Our docker image should support this already, but I am not sure about the main pipeline (and very likely not self serve)

[mjkkirschner]

we should delete this project.

[QilongTang]

Totally, is this the js version pm client?

[mjkkirschner]

yes, we can remove this at any time.

[QilongTang]

I see, seems it is in the repo but not part of the solution, so little risk

[mjkkirschner]

What do you think of also adding a tooltip here? to the filter icon if it doesn't exist already?

[QilongTang]

I can apply the same tooltip which I just added also to the context options, but the button I think need some different messaging?

[QilongTang]

@mjkkirschner More tooltips added

[QilongTang]

@mjkkirschner Let me know if you prefer more changes on this one. Otherwise trying to get a real build by demo tomorrow

[mjkkirschner]

@QilongTang LGTM - I had some alternative tooltip text for you to consider first though.