Update data path to /exports/mybeamline/data for training rigs

[ZohebShaikh]

Fixes #ISSUE

Instructions to reviewer on how to test:

1. Run system test on training rigs

Checks for reviewer

• Would the PR title make sense to a scientist on a set of release notes
• If a new device has been added does it follow the standards
• If changing the API for a pre-existing device, ensure that any beamlines using this device have updated their Bluesky plans accordingly
• Have the connection tests for the relevant beamline(s) been run via dodal connect ${BEAMLINE}

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.67%. Comparing base (dfc171c) to head (ff3fa08).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1039      +/-   ##
==========================================
+ Coverage   97.64%   97.67%   +0.03%     
==========================================
  Files         159      159              
  Lines        6590     6590              
==========================================
+ Hits         6435     6437       +2     
+ Misses        155      153       -2     

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

[ZohebShaikh]

This PR was created due to commit, which changes the path from /data to /exports/mybeamline/data/.

Currently, the apps are pointing to a specific branch in apps/values.yaml. This PR is in draft status and can be merged once the referenced branch is merged and a release is created.

@keithralphs This is the change I had to make when running the system test during the previous sprint.