Extended plotting functionality for Single Crystal Elastic mode of DNS Reduction GUI

[koshchii]

Description of work

This PR contains extended plotting functionality for Single Crystal Elastic mode of the DNS Reduction interface. In particular, the "Plot View" menu of the plotting tab contains options for selection of different types of interpolation, axes selections and plot types.

This PR also completes full integration of the Single Cristal Elastic mode into the DNS Reduction GUI.

Resolves part 6d of #36407.

To test:

• Download test data: Single_Crystal_Elastic.zip
• Open the reduction GUI [Interfaces->Direct->DNS Reduction]
• The "Single Crystal Elastic" mode should open by default. If not, switch to this mode, by selecting Tools -> Change Mode -> Single Crystal Elastic
• Make sure that the corresponding documentation is up-to-date (run cmake --build . --target docs-html in build folder to create docs). Relevant documentation will then be located in [mantid_build_path]/docs/html/interfaces/direct/dns_reduction/
• Browse to the directory where the test data are located using the "Paths" tab of the GUI
• Load and select the sample data for reduction using the "Data" tab
• Click on the "Options" tab and select options for data reduction.
• Proceed to the "Script Generator" tab and click on the "Generate and Run Script" button, which should run the corresponding workflow depending on the parameters selected under the "Options" tab.
• Open the "Plotting" tab and make sure that the images are generated.
• Use "Plot View" menu to switch between different "Plot type", "Axes", and "Interpolation" options and make sure that those work as expected.

---

Reviewer

Your comments will be used as part of the gatekeeper process. Comment clearly on what you have checked and tested during your review. Provide an audit trail for any changes requested.

As per the review guidelines:

• Is the code of an acceptable quality? (Code standards/GUI standards)
• Has a thorough functional test been performed? Do the changes handle unexpected input/situations?
• Are appropriately scoped unit and/or system tests provided?
• Do the release notes conform to the guidelines and describe the changes appropriately?
• Has the relevant (user and developer) documentation been added/updated?

Gatekeeper

As per the gatekeeping guidelines:

• Has a thorough first line review been conducted, including functional testing?
• At a high-level, is the code quality sufficient?
• Are the base, milestone and labels correct?

[github-actions]

This pull request has been automatically marked as stale because it has not had activity in 3 months. It will be closed in 7 days if no further activity occurs.
Allowing pull requests to close as stale helps us filter out old work that is no longer relevant and helps developers focus on reviewing current work.
All pull requests closed by this bot act like normal pull requests; they can be searched for, commented on or reopened at any point.
If these changes are still relevant then please comment and tag @mantidproject/gatekeepers to highlight that it needs to have a reviewer assigned.

[github-actions]

👋 Hi, @koshchii,

Conflicts have been detected against the base branch. Please rebase your branch against the base branch.