Add smoke tests to CI workflow for verifying build artifacts

[Ripan-Roy]

This PR (#3319) refactors the CI workflow to move smoke tests for distribution artifacts (sdist and wheel) from the build job into a new dedicated smoke-tests job.

Changes

• Created a new smoke-tests job that runs after the build job.
• Moved existing sdist smoke tests (test collection comparison) from the build job.
• Added new wheel smoke tests.
• Updated the check job to depend on smoke-tests.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00000%. Comparing base (63ce968) to head (25757f1).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@               Coverage Diff               @@
##                 main        #3352   +/-   ##
===============================================
  Coverage   100.00000%   100.00000%           
===============================================
  Files             125          125           
  Lines           19388        19388           
  Branches         1319         1319           
===============================================
  Hits            19388        19388           

🚀 New features to boost your workflow:

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

[A5rocks]

Makes sense to me! Generally our CI is slower than I'd like, so saving 15~30 seconds is nice.

[trio-bot]

Hey @Ripan-Roy, it looks like that was the first time we merged one of your PRs! Thanks so much! 🎉 🎂

If you want to keep contributing, we'd love to have you. So, I just sent you an invitation to join the python-trio organization on Github! If you accept, then here's what will happen:

• Github will automatically subscribe you to notifications on all our repositories. (But you can unsubscribe again if you don't want the spam.)

• You'll be able to help us manage issues (add labels, close them, etc.)

• You'll be able to review and merge other people's pull requests

• You'll get a [member] badge next to your name when participating in the Trio repos, and you'll have the option of adding your name to our member's page and putting our icon on your Github profile (details)

If you want to read more, here's the relevant section in our contributing guide.

Alternatively, you're free to decline or ignore the invitation. You'll still be able to contribute as much or as little as you like, and I won't hassle you about joining again. But if you ever change your mind, just let us know and we'll send another invitation. We'd love to have you, but more importantly we want you to do whatever's best for you.

If you have any questions, well... I am just a humble Python script, so I probably can't help. But please do post a comment here, or in our chat, or on our forum, whatever's easiest, and someone will help you out!