ci: Use cargo nextest for testing in CI

[mhovd]

Should speed up tests in CI

[github-actions]

Bencher Report

Project	PMcore
Branch	cargo-nextest
Testbed	mhovd-pgx

Click to view all benchmark results

Benchmark	Latency	Benchmark Result milliseconds (ms) (Result Δ%)	Upper Boundary milliseconds (ms) (Limit %)
bimodal_ke_npag	📈 view plot 🚷 view threshold	4,285.60 ms (-12.65%) Baseline: 4,906.32 ms	6,113.39 ms (70.10%)
bimodal_ke_npod	📈 view plot 🚷 view threshold	1,448.40 ms (+0.55%) Baseline: 1,440.50 ms	2,121.87 ms (68.26%)
bimodal_ke_postprob	📈 view plot 🚷 view threshold	521.79 ms (+43.10%) Baseline: 364.64 ms	926.99 ms (56.29%)

🐰 View full continuous benchmarking report in Bencher

[Copilot]

Pull request overview

This PR updates the Rust CI workflow to use cargo-nextest for running tests, aiming to reduce overall CI runtime while also producing JUnit output for reporting.

Changes:

• Install cargo-nextest in CI and switch cargo test invocations to cargo nextest run --profile ci across feature sets.
• Add a nextest CI profile in .config/nextest.toml, including retries and JUnit XML output configuration.
• Upload and publish JUnit test reports from Nextest runs, and grant the workflow checks: write permission to publish check-based reports.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
.github/workflows/rust.yml	Switches test execution to cargo nextest, adds JUnit artifact upload + check report publishing, and updates permissions for report publication.
.config/nextest.toml	Introduces Nextest profiles (default, ci) including timeouts, retries, and JUnit output path.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.