Fix/context macro conflict

[gauravharsha]

Timing jitter assertion in Test Accumulate section is non-fatal on loaded CI runners: emits a WARN if jitter exceeds 10ms threshold, but falls through to a hard REQUIRE on clean workstations where the assertion is expected to pass.

Also updates README.md for the changes in #5

[Copilot]

Pull request overview

This PR reduces test flakiness in the timing accumulator tests by making one jitter assertion non-fatal (warning-only) when the measured jitter exceeds the existing threshold, and updates the README’s mpi_context access example to use the documented context() accessor.

Changes:

• In Test Accumulate, replace a hard failure on timing jitter with a WARN when jitter exceeds 1e-2 seconds.
• Update README examples from mpi_context::context.* to mpi_context::context().*.

Reviewed changes

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

File	Description
test/utils_test.cpp	Makes the timing jitter check warning-only when it exceeds the threshold to reduce CI flakiness.
README.md	Fixes the documented mpi_context usage to call context() before accessing members.

---

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

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 71.09%. Comparing base (bbd4270) to head (99ed49d).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main       #6   +/-   ##
=======================================
  Coverage   71.09%   71.09%           
=======================================
  Files           4        4           
  Lines         211      211           
=======================================
  Hits          150      150           
  Misses         61       61           

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