Make `serviceVersion` search query parameter semver aware

[confused-Techie]

Make it so that a search for serviceVersion with the value 3.0.0 will match a declaration of 3-4, most important on the consumer side, although shouldn't be too difficult to add across the board.

[savetheclocktower]

Feels a bit hard on the postgres side, no? Like a custom SQL function? (Not that it's impossible, since postgres can probably do anything.)

[confused-Techie]

@savetheclocktower I'm thinking it may be best to pull all packages that provide x service, then filter those in JS using the semver module and remove those that don't match.

Tbh, I'm rather curious about the performance, since I've always had my concerns about adding all of our semver based logic into the SQL side. So if anything it might provide us a good test case for something that won't have a huge impact if the performance isn't great.

[savetheclocktower]

Honestly, you're right — at the scale we're talking about, it doesn't have to be implemented in postgres. Probably a bit tricky to filter after the fact when it comes to pagination and such, but still likely easier than a custom function.

[confused-Techie]

Good call on the fact we'd have to manually update pagination info, since that is generated during the original Postgres call, so that might be somewhat tricky, but as long as we are aware of it, hopefully not too bad.