Search UI add issue scope results filtering by state

What does this MR do?

Issue #237932 (closed)

Allow users doing Basic (PostgreSQL backed) or Advanced (Elasticsearch backed) search to filter issue scope results by the state field (all, opened, closed). The filtering changes are applied at the Global, Group, and Project search levels.

Updated and added new tests.

To test this manually you will need to have Elasticsearch setup and Advanced Search enabled for at least 1 project.

Videos

Video showing Basic Search

global-basic-search

group-basic-search

project-basic-search

Video showing Advanced Search

global-advanced-search

group-advanced-search

project-advanced-search

Does this MR meet the acceptance criteria?

Conformity

• Changelog entry
• Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• Tested in all supported browsers
• [-] Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• [-] Label as security and @ mention @gitlab-com/gl-security/appsec
• [-] The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• [-] Security reports checked/validated by a reviewer from the AppSec team

app/assets/javascripts/pages/search/show/index.js

 import Search from './search';
-import initStatusFilter from '~/search/status_filter';
+import initStateFilter from '~/search/state_filter';
 
 document.addEventListener('DOMContentLoaded', () => {
-  initStatusFilter();
+  initStateFilter();
   return new Search();
 });