[MRG] handle (0028,0101) "Bits Stored" in numpy handler

[pbailey-hf]

Describe the changes

Handle the "Bits Stored" tag when interpreting pixel data in the numpy handler.

Tasks

• Unit tests added that reproduce the issue or prove feature is working
• Fix or feature added
• Code typed and mypy shows no errors
• Documentation updated (if relevant)
  • No warnings during build
  • Preview link
• Unit tests passing and overall coverage the same or better

[pbailey-hf]

This addresses an issue similar to #1149 when interpreting pixel data with the numpy handler.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.19%. Comparing base (5612f56) to head (b06c9a5).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2026   +/-   ##
=======================================
  Coverage   98.19%   98.19%           
=======================================
  Files          73       73           
  Lines       12203    12209    +6     
=======================================
+ Hits        11983    11989    +6     
  Misses        220      220           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[scaramallion]

The current pixel_data_handlers backend is probably going to be deprecated in the v3.0 release, so this should really be added to the _apply_sign_correction() function in pixels.decoders.base with an updated DecodeRunner._test_for("sign_correction").

DICOM reference is Part 5, Section 8. One thing I haven't noticed before (in relation to the High Bit value):

Receiving applications may not assume anything about the contents of unused bits, and in particular may not assume that they are zero, or that they contain sign extension bits.

This may end up causing some issues with the way view_only works, annoyingly...

[pbailey-hf]

Thanks for the feedback. I'll rework it soon.