Move sans gui out of framework to mantidqtinterfaces

[jhaigh0]

Description of work

Move the gui_logic out of scripts/sans to a new mantidqtinterfaces dir.
This probably all needs a bit of a refactor but I'm trying to do the minimal changes possible in this pr.

A few things I want opinions on:

• 8f76daf The RowEntries model (previously in gui_logic/models) has been refactored out to a file now in sans/data_objects. This is because it was being used by the command interface (in particular the csv parser) so I needed to eliminated the link between scripts and code which was now in mantidqtinterfaces. Not sure if data_objects is the best dir to put it in?
• c52af98 I don't think it is strictly necessary to move this System test, I'm in two minds about it. I moved it out of framework to qt because it now imports from mantidqtinterfaces, but it does split it up from all the other sans systerm tests.

It might be good to checkout this branch (or user git test-pr to view the file tree in an IDE to get a good sense of where things have moved to. It's hard to follow on github I think.

The goal of this is to eventually remove the qt dependency from the mantid package. There are still a few more places to sort out for this to happen, but this is the majority of it I think.

Closes #37952

To test:

• Could go through the sans gui manual testing https://developer.mantidproject.org/Testing/SANSGUI/ISISSANSGUITests.html

Build testing all tests on all branches https://builds.mantidproject.org/job/build_branch/1474/

---

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?
• If the PR author isn’t in the mantid-developers or mantid-contributors teams, add a review comment rerun ci to authorize/rerun the CI

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]

👋 Hi, @jhaigh0,

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

[MialLewis]

Have tested the SANS interface via the manual testing instructions, all appears in working order.

The movement of RowEntries and the system test make sense to me.

[cailafinn]

Just one comment on the refactored row_entries.py file.

[cailafinn]

If this file is now a duplicate of the new one in the framework, could this file be deleted and any imports be moved to the one in the framework?