fix(engine-core): data proxy integration patch version resolver

[millsp]

Fixes the automatic data proxy version resolution for patch-dev releases.

[Jolg42]

Related 3.15.1-dev.1 2 tests failures for dataproxy
https://prisma-company.slack.com/archives/CRGDU19K6/p1654689974210099

[Jolg42]

Tried a few to check

https://unpkg.com/prisma@%3C=3.9.2-dev.1/package.json returns 3.9.2-dev.1 🔴 expected 3.9.1
https://unpkg.com/prisma@%3C=3.9.2-dev.2/package.json returns 3.9.2-dev.2 🔴 expected 3.9.1
https://unpkg.com/prisma@%3C=3.9.1-dev.1/package.json returns 3.9.1-dev.1 🔴 expected 3.9.0

If I remove the = in <=

https://unpkg.com/prisma@%3C3.9.2-dev.1/package.json returns 3.9.1 🟢 expected 3.9.1
https://unpkg.com/prisma@%3C3.9.2-dev.2/package.json returns 3.9.2-dev.1 🔴 expected 3.9.1
https://unpkg.com/prisma@%3C3.9.1-dev.1/package.json returns 3.9.0 🟢 expected 3.9.0

So this works better for patches here but only for the first patch-dev version.

For dev versions it's the same

https://unpkg.com/prisma@%3C3.16.0-dev.14/package.json returns 3.16.0-dev.13 🔴 expected 3.15.0
https://unpkg.com/prisma@%3C3.16.0-dev.1/package.json 3.15.0 🟢 expected 3.15.0

[Jolg42]

Oh ok you remove the suffix when sending the url to make it work 😓

See suggestion to improve comment

[Jolg42]

Note if we use <= then we could get different results once a release happen, before the release happens the previous version will be chosen and after the current one, just something to be aware of I guess.

[Jolg42]

It's out in 3.16.0-dev.16