Advanced search UI

[g-saracca]

What this PR does / why we need it:

Replicates the Advanced Search UI from the JSF version.
Introduces a mechanism to retain the user's previous advanced search within a specific collection, allowing the form to be pre-filled when performing a new advanced search. This uses localStorage (though sessionStorage could also have been used).
Additionally, it persists the currently selected facet filter queries when performing an advanced search.
This video explains the above

advanced-search-additions.mov

Which issue(s) this PR closes:

• Closes Advanced Search UI #760
• Could close Feature Request/Idea: Allow filtering by publication status; e.g. unpublished, published, draft; from advanced search page dataverse#9993

Related PRs:

• Depends on Include isAdvancedSearchFieldType property dataverse#11617
• Depends on Include isAdvancedSearchFieldType property dataverse-client-javascript#333

Suggestions on how to test this:

Step 1: Run the Development Environment

1. Execute npm i.
2. Navigate with cd packages/design-system && npm i && npm run build.
3. Return with cd ../../.
4. Ensure you have a .env file similar to .env.example
5. Navigate with cd dev-env.
6. Start the environment using ./run-env.sh 11614-include-isAdvancedSearchField-property .
7. To verify the environment, visit http://localhost:8000/ and check your local Dataverse installation.

Step 2:

1. Log in and create different collections, datasets and/or files.
2. Go to the Root collection and click the "Advanced Search" link next to the search input.
3. Validate that the form has the same fields as in the JSF version (you can also try on different collections configured with different metadata blocks)
4. Enter some values and click "Find" (enter same values at the same time in the JSF version), you should be redirected to the collection page.
5. Validate that the search input is pre-filled with the advanced search query and this one is the same as in the JSF version.
6. Click on the "Advanced Search" link again and the form should be populated with the previous search.
7. Click the "Clear Form" to reset the form values.
8. Follow the same steps, but this time apply some facet filters before clicking the "Advanced Search" button. After performing the advanced search, the previously selected facet filters should still be persisted and reflected in the collections page UI, as long as the advanced search returned results.

Does this PR introduce a user interface change? If mockups are available, please link/include them here: Yes.

Is there a release notes update needed for this change?:

N/A

Additional documentation:

N/A

[coveralls]

coverage: 97.535% (-0.5%) from 98.058%
when pulling 1cead0b on feat/760-advanced-search-ui
into 96d881e on develop.

[g-saracca]

@ekraffmiller could you take a look? I just changed a missing import and merged with develop.
About test/component failing, I've left a message in our channel, it's not the tests but the coveralls report failing 👍🏼

[ekraffmiller]

looks good, approved

[ofahimIQSS]

Hello! Please resolve the branch conflicts - I am ready to merge this afterwards.

[g-saracca]

@ofahimIQSS, done, ready to merge!

[ofahimIQSS]

Very nice - merging PR!