🐛 feat(containers/managers) return a warning when an automatically resolved time stamp is different from 0.0 and (sample) fix fields summarize in str

[casenave]

Checklist

• Typing enforced
• Documentation updated
• Changelog updated
• Tests and Example updates
• Coverage should be 100%

🔗 Related issues (optional)

Closes #314

With the MNWE provided in the related issue, thie PR outputs:

Sample(2 globals, 2 timestamps, 5 fields)
--
[2026-02-23 22:35:04,745:WARNING:default_manager.py:resolve_time(224)]:A time stamp has been automatically resolved at 1.0
[2026-02-23 22:35:04,746:WARNING:default_manager.py:resolve_time(224)]:A time stamp has been automatically resolved at 1.0
[2026-02-23 22:35:04,746:WARNING:default_manager.py:resolve_time(224)]:A time stamp has been automatically resolved at 1.0
[2026-02-23 22:35:04,746:WARNING:default_manager.py:resolve_time(224)]:A time stamp has been automatically resolved at 1.0
Sample(2 globals, 1 timestamp, 5 fields)

[casenave]

@daviddanan we can discuss here the solution I propose to #314
The warning may introduce a lot of noise.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!