Update Notification for non-release versions does not work

[pljones]

Describe the bug

It looks like there's a bug in the version comparison between a non-release version of the client/server that's checking it's own version and the source version number.

For example "3.12.0rc1" isn't getting flagged that there's an update available when an update server has "3.12.0" available. "3.11.0" works fine.

I think any string other than dev* should sort before the release, with dev* sorting after the release.

To Reproduce

In all the following cases, the version chosen should be before the current release.

1. Install a release version of the client or server with a version number less than current, run the GUI
2. See the notification of an update
3. Install a development version of the next release (3.x.xdev...), run the GUI
4. See the notification of an update
5. Install a tagged pre-release version of the next release (tag in "alpha*", "beta*" and "rc*"), run the GUI

Expected behavior

1. See the notification of an update

[softins]

I think any string other than dev* should sort before the release, with dev* sorting after the release.

Yes, that's what I have done in Jamulus Explorer since its early days, and I did the same in Jamulus recently when adding version sorting to the connect dialog.

[softins]

Although in fact, I specifically made "alpha", "beta" and "rc" sort before, and any other suffix sort after the bare version number. And helpfully, alpha, beta and rc are already in alphabetical order.

[pljones]

The problem is 3.12.0rc1 comes before 3.12.0 -- the current check doesn't do this, from what I'm seeing. Only dev* should come "after" the semantic version it's appended to.

[ann0see]

Which may have been the reason why we used 3.(x-1).0rc1 before...