New version in the footer mismatch with actual latest version
Feature originally developed in https://github.com/pyroscope-io/pyroscope/pull/333
Here's an example posted in slack:
The user is running 0.2.4 but the message says 0.2.3 is the latest version!

This might be because of the resent split of the docs repo. I'll investigate

Still seeing this issue /cc @petethepig
I think it's a race condition where the demo gets deployed on the new version before we even update the latest-version.json on pyroscope.io
I'll figure something out..
After talking with @petethepig It looks like we need to parse semVer and check if the current version is smaller than the "newer" version.
https://github.com/pyroscope-io/pyroscope/blob/main/webapp/javascript/components/Footer.tsx#L35