Add tracking between axis title, window title, and plot name

[jhaigh0]

Description of work

When the user edits the title of a single plot (any non-tiled plot), the window name and plot name will be updated to match. This also works in reverse, if you change the plot name in the plot selector widget, it will change the window title and plot title.

Summary of work

I've added a callback to the axis title using the matplolib add_callback method so that any time it is changed a function will trigger.
Also added a method to the figuremanager to edit the axis title, so it can be called from the plot selector.

The callback is set up in the show method rather than the constructor, since upon construction there are no axes added to the plot. It also had to be contained within the figuremanager class so that this would work with script generated plots.

Fixes #33224

To test:

• Load some data
• Plot a spectrum
• This should be as before, axis title is dataset name, window and plot name are datasetname-1
• Double-click the plot title and change it, window title and plot name should update
• Go to the plot settings and change the title from there, window title and plot name should update
• Hide the plot using the eye icon
• Rename the plot in the plot selector (lower left)
• Unhide the plot and the window and axis title should be renamed
• Do some testing with other kinds of mantid plots, check that setting a tiled plot axis name has no effect
• Test with script made plots (some good ones here

---

Reviewer

Please comment on the points listed below (full description).
Your comments will be used as part of the gatekeeper process, so please comment clearly on what you have checked during your review. If changes are made to the PR during the review process then your final comment will be the most important for gatekeepers. In this comment you should make it clear why any earlier review is still valid, or confirm that all requested changes have been addressed.

Code Review

• Is the code of an acceptable quality?
• Does the code conform to the coding standards?
• Are the unit tests small and test the class in isolation?
• If there is GUI work does it follow the GUI standards?
• If there are changes in the release notes then do they describe the changes appropriately?
• Do the release notes conform to the release notes guide?

Functional Tests

• Do changes function as described? Add comments below that describe the tests performed?
• Do the changes handle unexpected situations, e.g. bad input?
• Has the relevant (user and developer) documentation been added/updated?

Does everything look good? Mark the review as Approve. A member of @mantidproject/gatekeepers will take care of it.

Gatekeeper

If you need to request changes to a PR then please add a comment and set the review status to "Request changes". This will stop the PR from showing up in the list for other gatekeepers.

[jclarkeSTFC]

Looks good, works as expected