Polarized SANS metadata: apply user file settings in SANS reduction save

[rbauststfc]

Part of #36147. See the design and requirements documents, and the NXcanSAS specification proposal, that are linked on that issue for more details of what needs to be implemented.

In the SANS reduction workflow, we need to the use the polarized SANS settings that we have stored in the state object to do the following:

• If required, overwrite parameter values and/or move the location of relevant polarizing components in the IDF.
• If under Polarized SANS metadata: add user file definition and ability to parse inputs #38524 we have decided not to handle this in the user file parser, we will need to load any efficiency, transmission or empty cell data that has been provided by file.
• Pass relevant metadata from the state object to relevant properties of the SANSSave algorithm. The SANSSave algorithm will also need to start accepting a workspace group/workspace list.
• I think we will need to refactor/extend the save workflow in the reduction slightly, because at the moment it looks like the code loops through a list of workspace names and saves them individually. For polarised reductions we will want to save multiple workspaces into the same file, so we will need a pathway that does this.

We will need to ensure the following:

• We don't break the Save Other button functionality in the SANS GUI. Most of the reduction code and integrated save workflow is common to both the GUI and the command interface. It's out of scope to support saving polarized SANS metadata via the GUI at this stage (this includes via the Save Other button in the GUI), but we obviously need to make sure that changes we make do not have any negative consequences for the GUI reduction.
• That the save works correctly when performing a reduction via a script using the ISIS SANS command interface.

This issue should not be worked on until #38524 has been completed.