add data_release_prevention_reason attribute to mlwh

[wendyyang]

Closes #

Changes proposed in this pull request

export data_release_prevention_reason to MLWH

Instructions for Reviewers

[All PRs] - Confirm PR template filled
[Feature Branches] - Review code
[Production Merges to main]
    - Check story numbers included
    - Check for debug code
    - Check version

[codecov]

Codecov Report

❌ Patch coverage is 28.57143% with 10 lines in your changes missing coverage. Please review.
✅ Project coverage is 84.79%. Comparing base (9387bea) to head (b907634).

Files with missing lines	Patch %	Lines
...t_studies_with_data_release_prevention_reason.rake	23.07%	10 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #5935      +/-   ##
===========================================
- Coverage    84.86%   84.79%   -0.08%     
===========================================
  Files         1495     1496       +1     
  Lines        33982    33996      +14     
  Branches      3621     3623       +2     
===========================================
- Hits         28840    28826      -14     
- Misses        4289     4321      +32     
+ Partials       853      849       -4     

Flag	Coverage Δ
javascript	76.31% <ø> (ø)
ruby	84.66% <28.57%> (-0.10%)	⬇️

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

☔ View full report in Codecov by Harness.
📢 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.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[andrewsparkes]

Looks Ok to me.
Rebroadcasting all the studies at once may slow, test this in case you need to do it in smaller batches. Hopefully fine.