fix(DicomWebDataSource): allow custom headers in requests

[achandra-rp]

Introduces a requestOptions field to DicomWebConfig allowing custom headers to be specified for DICOMweb requests. Refactors header handling to merge custom and authorization headers, ensuring all requests can include additional user-defined headers.

Context

Changes & Results

Testing

Checklist

PR

• [√] My Pull Request title is descriptive, accurate and follows the
  semantic-release format and guidelines.

Code

• [√] My code has been well-documented (function documentation, inline comments,
  etc.)

Public Documentation Updates

• [N/A] The documentation page has been updated as necessary for any public API
  additions or removals.

Tested Environment

• [] OS: macOS
• [] Node version: v25.2.1
• [] Browser: Chrome

Context:

• “Enable custom DICOMweb headers (e.g., Rp‑Vna‑Site‑Id) via requestOptions.headers.”

Changes & Results:

• “Allow arbitrary headers in RequestHeaders and pass requestOptions.headers through DICOMweb clients.”

Testing:

• “Built OHIF with PUBLIC_URL=/ohif and verified /ohif loads; verified /ohif/proxy/.../query/studies?limit=1 returns 200; verified custom Rp‑Vna‑Site‑Id via query param.”

[netlify]

✅ Deploy Preview for ohif-dev ready!

Name	Link
🔨 Latest commit	ddefe7d
🔍 Latest deploy log	https://app.netlify.com/projects/ohif-dev/deploys/6949c0f286a28f00083d0502
😎 Deploy Preview	https://deploy-preview-5675--ohif-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.