What this PR does / why we need it:

Adds the facet filtes in the Collection Page.
See original issue

Which issue(s) this PR closes:

• Closes Collection Page: add Collection Facets #562

Special notes for your reviewer:

Wait to test until #563 is merged and I update this branch with develop.

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, with the variable VITE_DATAVERSE_BACKEND_URL=http://localhost:8000.
5. Navigate with cd dev-env.
6. Start the environment using ./run-env.sh unstable.
7. To verify the environment, visit http://localhost:8000 and check your local Dataverse installation.

Step 2: Test the feature

1. Create some collections and datasets in the root collection. Add one or multiple files in one of those created datasets.
2. Navigate to http://localhost:8000/spa/collections and in another tab to http://localhost:8000 and apply same filters in the SPA version and JSF version (search; filter by collection, datasets or files; select and remove facets). Check that they show the same items and facets list.
   *Note that for now, for the selected facets button labels, we are only showing the facet value, so when in the JSF version you will see "Author Name: John" in the SPA you will just see "John".

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?:

No

Additional documentation:

No