fix(goatcounter): properly count SPA page hits

[necauqua]

On the surface it seems that only google and plausible scripts handle
the SPA correctly - but I don't know if maybe others handle
window.history API themselves somehow or something like that.

However, I am trying out goatcounter and in it's docs I see that it
does no special SPA handling, so this has to be added.

Note:
The whole significantLoad thing is to correctly count things -
goatcounter will not be loaded and initialized yet when the initial
"nav" is dispatched (because of the weird dynamic script tag insertion
thing you guys have going on here), but it will count that page load
when it itself is loaded.

If there was a way to ensure goatcounter is loaded before the first
nav, you could just configure it to not count anything on it's own load
(like in their spa example) and
have the "nav" call it unconditionally, but that's not the case 🤷

[necauqua]

So I finally actually deployed a quartz site and I tested the goatcounter thing - apparently my previous fix didn't quite work.

The new way (force-pushed) is the only one I've found to actually work relatively reliably at least.

[aarnphm]

plausible works given that the plausible script will attach a window.plausible :)

[aarnphm]

Can you check again if this works?

[necauqua]

Owie owie owies, what did you do to the branch lol

Anyway, re-tested your exact commit to be sure, but just "spa-preserve" like that does nothing - it only counts the first pageload.
Adding "spa-preserve" and then calling goatcounter api on nav events for some reason doubles the amount of hits on every hit - I mentioned that in the updated comment description.

The only thing that seemingly worked great is this ugly re-adding the script on nav events - at least the script itself is cached, and also tiny so not like we re-execute alot, pfew