Use int for algorithm property when calling python algorithm from c++

[robertapplin]

Description of work

This PR fixes an error when attempting to use a long instead of an int for a property of a python algorithm. when calling the python algorithm from C++.

Attempt to assign to property (SampleBins) of incorrect type

There was a recent change in behaviour for the PropertyWithValue class introduced in #37196 which caused this problem.

There is no associated issue.

To test:

1. Go to Inelastic Bayes Fitting interface
2. Go to Quasi tab
3. Load the 26176 red from the sample data sets for sample
4. Load the 26173 res from the sample data sets for resolution
5. Click Run. It should run successfully

This does not require release notes because it is a regression since the last release

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.

[sf1919]

Should this have a 6.11 milestone instead? The error was introduced into main so will not be in release-next

[robertapplin]

Should this have a 6.11 milestone instead? The error was introduced into main so will not be in release-next

Oops, no it should be 6.10 but I forgot to change the base branch! I think the error is in release-next

[cailafinn]

Is it possible to write a unit test for this? Doubly important when we can't rely on the compiler to get the typing right.

[robertapplin]

Is it possible to write a unit test for this? Doubly important when we can't rely on the compiler to get the typing right.

Its not easy to add a test for this because the code in this area is not in MVP and has Qt everywhere. Instead I have opened a new issue to add manual testing instructions for Inelastic Bayes Fitting. This would catch the problem in the future #37455

[cailafinn]

Questions addressed. Code looks good, it's a minor change. Performed functional tests in description and no longer throws/crashes. Thanks for opening that issue!