Feature/381 implement lazy loading

[g-saracca]

What this PR does / why we need it:
Implements lazy loading of pages in router.
To load only necessary/related js files for the current page.

Which issue(s) this PR closes:

Closes #381

Special notes for your reviewer:

Suggestions on how to test this:

Step 1: Run the Development Environment

1. Execute npm i.
2. Navigate with cd packages/design-system && 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.

Step 2: Run e2e and component tests and check everything keeps working as expected.

Step 3: The best way to test this is to test in beta environment once deployed.

Checking in the console the network traffic, specifically with the JS tab selected and confirm that only the necessary files are loaded.
I recommend opening each url of the app in a window in incognito mode to avoid caching and loading files belonging to chrome extensions or the browser used.

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

Yes, a new Spinner component has been created in the design system. This Spinner works as a backup rendered element while the JS files are lazily loading. This spinner will only be visible the first time the files are loaded.

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

Additional documentation:
Lazy Loading implementation
Here are some screenshots of the load differences.
Screenshots of the application views were taken in an incognito window to avoid showing file loading from Chrome extensions and to avoid caching.
Each page was loaded at the specified url directly.

Building the app. 👇
With lazy loading.

Without lazy loading.

Collections page
Resources transfered reduced from 1.4MB to 1.1MB.

With lazy loading.

Without lazy loading.

Create dataset page
Resources transfered reduced from 1.4MB to 944kb.

With lazy loading.

Without lazy loading.

[GPortas]

@GermanSaracca can you please resolve the merge conflicts?

[g-saracca]

Could we wait for merging this until we have fix e2e tests? I want to double check if this lazy loading of modules doesn't conflicts with any test.

[coveralls]

coverage: 97.814% (+0.005%) from 97.809%
when pulling 541c0e7 on feature/381-implement-lazy-loading
into d2789fc on develop.

[g-saracca]

Closed for now, until we can find the time to analyze more closely why the Suspense fallbacks are showing up more than once and why it is affecting e2e test only on github actions not on our end.