Aggregation should support all version tags

[timwoj]

A user recently ran into a problem with the ja4 package where they encountered a bug that had been fixed and released, but the repo had used version names that that didn't fit our expected vX.Y.Z naming. The package aggregation job in the packages repo ignored these versions, and so we never picked up that there was a new release. We requested the maintainer release a new version that matches our apparently-required naming scheme, which fixed the user's problem.

We should look at fixing the aggregation to handle other version schemes, or not have a requirement and just accept whatever tagging package maintainers want to use.

[bbannier]

The tricky bit here is that we rely on version strings to somehow resemble semantic versioning (we don't do exactly semantic versioning though). By accepting any version format we wouldn't know whether e.g., a187147269586392c03c44174d548b6a3394d141 was before or after bef7699ebf06284000d5a771a45b724dfb2709e2, so we would have no idea whether we needed to upgrade a package.