Enable cargo-nextest for CI

[lexnv]

To avoid issues with the CI, the nextest was replaced with cargo test.

This PR ensures we utilize it again the cargo nextest functionality, via
installing it locked (commit)

Issue reference: nextest-rs/nextest#306

Time Delta

Location	Sample 1	Sample 2	After 1	After 2
CI (ubuntu)	3m 10s	3m 1s	4m 47s	3m 23s
Windows	9m 33s	10m 15s	11m 18s	11m 34s
MacOS	8m 18s	5m 43s	8m 36s	9m 48s

Sample 1: 6fdb67f
Sample 2: bd31557.

[niklasad1]

nice,

it still doesn't support doc tests right?
might be good to add another job for that..

[alvicsam]

it still doesn't support doc tests right?

No, still not nextest-rs/nextest#16

I can suggest editing the test job in .gitlab-ci.yml. It runs on the parity CI runners which are way faster than GitHub runners. In this case the Continuous integration / Run tests Ubuntu (pull_request) GHA job can be removed. We also have a mac-runner but it's needed to test nextest on it. Unfortunately, we don't have windows runners so for them the only option is to use GHA.

[alvicsam]

This is not necessary, the image already contains cargo-nextest (not the latest version though)

[lexnv]

Thanks! I'll remove it, does cargo-hack also exist on the image?

[alvicsam]

No, we can add it if needed. But it might take some time when it reaches the production image

[jsdw]

So to confirm, it looks like nextest is actually taking longer than the old cargo test as it stands?

(Does that include the additional cargo test invocation that we need to run separate doc tests, and the time taken to download/install nextest?)

That being the case, I'd prefer to keep it simple and stick with cargo test until there is a clear advantage, or am I missing something?

[niklasad1]

So to confirm, it looks like nextest is actually taking longer than the old cargo test as it stands?

wow, I thought nextest was suppose to faster... but I think the UI/proc macro tests are the bottleneck

[jsdw]

Is the verdict to close this PR since nexttest is actually slower anyway (plus doesn't run doctests)?