LWS-209: Add spinner

[jesperengstrom]

Description

Adds a loading indicator

Tickets involved

LWS-209

Solves

No indication of anything happening when for example searching.

Summary of changes

• Added a progress bar (rather than a spinner) using the nProgress package. It runs on every navigation but i've added a small delay to avoid showing it on instant navigations. This can of course be tweaked further.
• With this in place, I tried removing the streaming of search results on resource pages. This would otherwise require a second spinner to replace the 'loading' text. I think this works well - with the indicator in place, it's quite satisfying to get the whole page at once.
• Made some minor related adjustments to the load function on the resource page. The getRelated() / await getRelated() call was done as the last thing before returning, not optimal when everything else is ready. We want to do it as soon as possible (i.e when there's a resourceId), but not wait for it, blocking subsequent operations. So we now make the call early and store the promise in a variable, awaiting it at the very end.

[johanbissemattsson]

LGTM! Awesome –  I agree that it's feels much more responsive and satisfying to navigate around now! 🌟

Good call with the getRelated promise 👍 We could maybe also achieve the same effect by implementing multiple parallel promises using promise.all in (or near) the return (instead of having to declare them as variables beforehand) but I think it's best done if we can do it together while pair programming.

[olovy]

LGTM
Agree that it feels more responsive!

Merging this.