Define setter for image.array to allow inplace operations

[sidneymau]

This pull request addresses #1272 by defining a setter for the Image.array attribute. This protects against any case where a user does an inplace operation on the image array attribute in an interactive environment: without the setter, this would raise an error while still performing the operation, leading to some confusion. This change also obviates the need to operate on a view of the underling array; e.g., instead of

image.array[:] += 1

we can now do

image.array += 1

[rmjarvis]

I'd like a few more tests that guarantee that the setter doesn't allocate new memory or change fundamental things about the array. I think the implementation is ok, but there are other ways to have written the setter which would pass this test, but would break the image object.
e.g.

image1.array = 1  # should keep array shape and dtype
image1.array = 1+2j  # should only work if array is already complex
image1.array = np.zeros((3,3))  # should only work if current shape is (3,3)

Also, all of those should fail if the image is a cont view.
In other words, try to come up with as many stress tests as possible and make sure it behaves as we would want it to behave.

[rmjarvis]

Also, this shouldn't be directed at releases/2.5. It's not a bugfix. Rebase it to main and direct the PR to main.

[sidneymau]

Evidently I don't know how to tell GitHub how to rebase, will try this in a new PR...