fix: Add traits module to reexport ThreadAware trait separately from derive macro

[Copilot]

Plan to (re-)export ThreadAware trait in thread_aware crate

• Create a new traits module in src/traits.rs
• Reexport the ThreadAware trait from the traits module
• Add the traits module to lib.rs as a public module
• Add #[doc(inline)] attribute to the trait reexport
• Add comprehensive documentation explaining the dual export
• Simplify documentation by removing Usage section
• Run tests to ensure no regressions
• Verify the trait can be imported from thread_aware::traits::ThreadAware

Original prompt

---

This section details on the original issue you should resolve

<issue_title>(re-)export ThreadAware trait in thread_aware crate</issue_title>
<issue_description>We need to (re-)export the ThreadAware trait from a module separate from the reexport in lib.rs so we can reexport it elsewhere without also reexporting the ThreadAware derive macro.

To do this we will make a traits module and reexport the trait from there.</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes (re-)export ThreadAware trait in thread_aware crate #179

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.0%. Comparing base (fa3a6db) to head (73c8b73).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #180   +/-   ##
=======================================
  Coverage   100.0%   100.0%           
=======================================
  Files          89       89           
  Lines        6217     6217           
=======================================
  Hits         6217     6217           

☔ 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.

[martin-kolinek]

Why not expose the trait directly from the core module?

[Darksecond]

The name traits was suggested for the module name, I can for sure just expose it from core.