Add time duration methods

[h-mayorquin]

Motivation

Previously discussed in slack. One difficulty that users have when building an NWBFile is to understand the overall time organization of the data. There is a push for providing better reporting of this and these methods would be useful in this context.

Checklist

• Did you update CHANGELOG.md with your changes?
• Have you checked our Contributing document?
• Have you ensured the PR clearly describes the problem and the solution?
• Is your contribution compliant with our coding style? This can be checked running ruff check . && codespell from the source directory.
• Have you checked to ensure that there aren't other open Pull Requests for the same change?
• Have you included the relevant issue number using "Fix #XXX" notation where XXX is the issue number? By including "Fix #XXX" you allow GitHub to close issue #XXX when the PR is merged.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.28%. Comparing base (c4dc960) to head (6a64a80).
⚠️ Report is 1 commits behind head on dev.

Additional details and impacted files

@@            Coverage Diff             @@
##              dev    #2146      +/-   ##
==========================================
+ Coverage   95.23%   95.28%   +0.04%     
==========================================
  Files          29       29              
  Lines        2876     2904      +28     
  Branches      740      748       +8     
==========================================
+ Hits         2739     2767      +28     
  Misses         83       83              
  Partials       54       54              

Flag	Coverage Δ
integration	73.89% <17.85%> (-0.55%)	⬇️
unit	85.08% <100.00%> (+0.14%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

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

[bendichter]

This looks great to me, thanks for working on this, @h-mayorquin ! I'd be interested in @oruebel 's thoughts as well

[oruebel]

I'd be interested in @oruebel 's thoughts as well

This is looks overall good to me. I added a few small suggestions, but overall this seems fine to me. I'll let @stephprince do final review and approval.

[rly]

Looks good to me. Thanks @h-mayorquin !

[bendichter]

this looks great. Once this is released, let's modify NWB inspector to use these methods.

Let's also port the Units table timing logic that is currently in the NWB Inspector library into PyNWB and do the same there.