ci: run clippy on features separately to find issues

[bantonsson]

Changes

This runs clippy on features separately to ensure that the code doesn't rely on other features being enabled.

Merge requirement checklist

• CONTRIBUTING guidelines followed
• Unit tests added/updated (if applicable)
• Appropriate CHANGELOG.md files updated for non-trivial, user-facing changes
• Changes in public API reviewed (if applicable)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 80.8%. Comparing base (da2029e) to head (99998fc).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##            main   #2866     +/-   ##
=======================================
- Coverage   80.8%   80.8%   -0.1%     
=======================================
  Files        124     124             
  Lines      23833   23836      +3     
=======================================
  Hits       19280   19280             
- Misses      4553    4556      +3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[cijothomas]

info: component 'clippy' for target 'x86_64-unknown-linux-gnu' is up to date
Updating crates.io index
Downloading crates ...
Downloaded cargo-hack v0.6.36
error: binary cargo-hack already exists in destination
Add --force to overwrite

@bantonsson Can you check this log from the CI run and see if this is to be fixed

[bantonsson]

@cijothomas The CI / lint script/job has now been fixed.

[cijothomas]

lint is now ~6-7 mins, previously ~3 mins.
This is still less than the longest CI check (Windows), so won't increase overall time.

[bantonsson]

So what is the process for getting this merged when it's been approved?

[bantonsson]

FYI, while this PR was waiting, a change missing this landed in main and wasn't caught by CI.

[cijothomas]

So what is the process for getting this merged when it's been approved?

https://github.com/open-telemetry/opentelemetry-rust/blob/main/CONTRIBUTING.md#how-to-get-prs-merged
Only maintainers have the access to "click the merge button". (same across entire Otel repos).
Nothing you need to do - some maintainer (most likely me!) will click the merge!