Expose cache_spec option in NWBHDF5IO.export

[rly]

Motivation

Right now, NWBHDF5IO.export always caches the spec. The option to change that is not exposed. This PR exposes that keyword argument. Ref: hdmf-dev/hdmf#1187

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.

[rly]

I don't think tests are necessary for this quick change, but I could write one if you think we should have it @stephprince

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.20%. Comparing base (71ef8e2) to head (124332d).
Report is 23 commits behind head on dev.

Additional details and impacted files

@@           Coverage Diff           @@
##              dev    #1959   +/-   ##
=======================================
  Coverage   92.20%   92.20%           
=======================================
  Files          27       27           
  Lines        2656     2656           
  Branches      693      693           
=======================================
  Hits         2449     2449           
  Misses        134      134           
  Partials       73       73           

Flag	Coverage Δ
integration	73.19% <ø> (ø)
unit	83.77% <ø> (ø)

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.

[stephprince]

Looks good to me! I think it is ok to not have tests for this small argument exposure.