Write outout files to an agreed location, to be copied elsewhere by another service.

[LilithCole]

Description of work

Changes the default locations for each of the output files to be generated. Once writing has finished, marks these files as read-only.

Ticket

Ticket234

Labels

Add appropriate label(s) to this PR

• 'bluesky-Semver-Major' - Breaking Change
• 'bluesky-Semver-Minor' - New feature
• 'bluesky-bug' - Bug fix
• 'bluesky-documentation' - Document Changes
• 'bluesky-ignore-for-release' - Do not show in the release notes

Labels can be found of the right-hand sidebar of this PR once created

Acceptance criteria

• Pull request title is understandable for a user (e.g. scientist) reading the release notes. The PR title should be a short description of the change from a user perspective.
• Pull request has appropriate labels for automatic release-notes generation
• File writing now points to c:\data\RB<rb_number>\bluesky_scans\
• File writing tests are changed to reflect this
• Once written fully, these files are marked as read-only

List the acceptance criteria for the PR. The aim is provide information to help the reviewer

Documentation

Highlight and provide a link to any additions or changes to the documentation, if applicable. The aim is provide information to help the reviewer
No change, implementing this https://isiscomputinggroup.github.io/ibex_bluesky_core/architectural_decisions/007-output-file-archiving.html