Run tests with nextest and publish results

[bantonsson]

What does this PR do?

This PR does the following:

• Adds the nextest test runner and configuration to run single threaded tests separately.
• Adds test result reporting as checks to the PR
• Renames the modules for single threaded tests to single_threaded_tests, so they can be easily run separately with nextest.
• Removes the use of ignore to separate out single threaded tests.
• Adds a skip_root_tests module name for tests (that were previously ignored 🤷🏼‍♂️) that can't run as root on GitLab CI.
• Changes the module name for most other tests to tests for consistency and easy skipping when building with cross, which doesn't support nextest.

Motivation

• Tests were using skip as a way to separate out different test configuration needs (single threaded tests).
• Failures were hard to find (scrolling through test output).

Additional Notes

Tests should now be run with cargo nextest run

To install nextest run:

cargo install --locked 'cargo-nextest@0.9.67'

or if you are on a rust version newer than 1.71.1 run:

cargo install --locked 'cargo-nextest@0.9.*'

Dependencies

This PR depends on new build images for the GitLab build.

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 76.47059% with 4 lines in your changes are missing coverage. Please review.

Project coverage is 65.36%. Comparing base (00e924b) to head (bb191a5).

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #415      +/-   ##
==========================================
+ Coverage   64.77%   65.36%   +0.59%     
==========================================
  Files         184      184              
  Lines       22326    22503     +177     
==========================================
+ Hits        14462    14710     +248     
+ Misses       7864     7793      -71     

Components	Coverage Δ
crashtracker	20.31% <0.00%> (-0.07%)	⬇️
data-pipeline	51.45% <ø> (ø)
data-pipeline-ffi	0.00% <ø> (ø)
ddcommon	81.23% <ø> (ø)
ddcommon-ffi	74.93% <ø> (ø)
ddtelemetry	53.72% <ø> (ø)
ipc	81.27% <ø> (+1.96%)	⬆️
profiling	76.89% <ø> (ø)
profiling-ffi	60.05% <ø> (ø)
serverless	0.00% <ø> (ø)
sidecar	29.37% <ø> (+0.70%)	⬆️
sidecar-ffi	0.00% <ø> (ø)
spawn-worker	54.98% <100.00%> (+4.48%)	⬆️
trace-mini-agent	69.12% <ø> (ø)
trace-normalization	97.79% <ø> (ø)
trace-obfuscation	95.74% <ø> (ø)
trace-protobuf	25.64% <ø> (ø)
trace-utils	68.85% <ø> (ø)

[danielsn]

What happens if someone runs cargo test?

[ekump]

looks good! Glad we can get rid of the ignore workflow for single-threaded tests.

[bantonsson]

@danielsn if you do cargo test, all tests will be run as normal, and some tests that need to be run single threaded will fail.

[morrisonlevi]

Looks fine to me, assuming CI passes and whatnot.