Incorrect empty state on milestones view when filter applied

Summary

The empty state suggests there are no open milestones when in fact there are, but they are filtered out.

Steps to reproduce

https://gitlab.com/groups/gitlab-org/-/milestones?search_title=hello&state=&sort=

image

Example Project

What is the current bug behavior?

What is the expected correct behavior?

We should probably be using the empty search results empty state: https://design.gitlab.com/patterns/empty-states#empty-search-results

Relevant logs and/or screenshots

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info 

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check 
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)


(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)


(we will only investigate if the tests are passing)

Possible fixes