NEX version checks update

[jonbarrow]

NEX versions are just semver, which are non-trivial to accurately compare against

For instance, in some cases we had checks such as major >= 3 && minor >= 5 for validating if something is above NEX 3.5.0. However this breaks down when we have instances where the NEX version is something like 4.0.0. Now suddenly this check fails, because even though 4 is greater than 3, the minor version is smaller

This PR does 3 things

• Convert our nex_version objects into semver strings
• Use the semver module to compare versions
• updates the nex/ version lists to all be the same. We track them separately because there are rare cases where certain protocols have different versions, however the vast majority of the time each has the same version. Any differences can just be patched in later

[jonbarrow]

We should add this on nex-go aswell

That's what I'm going to do next