Hard-code dtype_numpy for CMS Pilatus detectors

[Copilot]

This ports the Pilatus metadata workaround from the OPLS profile into cms-profile-collection. The change ensures CMS Pilatus detectors always report the expected NumPy dtype in their Bluesky data keys.

• What changed

  • Added a shared CMSPilatusDetector base class in startup/20-area-detectors.py.
  • Overrode make_data_key() to force dtype_numpy to "<i4" for Pilatus detector documents.

• Where it applies

  • Updated all local Pilatus detector variants to inherit from the shared base:
    • PilatusV33
    • Pilatus800V33
    • Pilatus2MV33
    • PilatusV33_h5
    • Pilatus800V33_h5

• Why this shape

  • Keeps the workaround centralized in one place instead of duplicating the override across each detector class.
  • Covers both TIFF- and HDF5-backed Pilatus configurations used by this profile.

class CMSPilatusDetector(PilatusDetector):
    def make_data_key(self):
        ret = super().make_data_key()
        ret["dtype_numpy"] = "<i4"
        return ret