Compute Operation ring removal

[ashmeigh]

Issue

This issue was part of #2051

Description

This pull request addresses the ongoing effort to standardize the execution of operations by transitioning from the partial function style to a structured compute_function approach. In this update, several operations have been refactored to adhere to the new standard. The modifications ensure a clearer separation between the setup and execution phases of each operation, improving the maintainability and readability of the codebase.

Changes

Refactored multiple operations to implement the new compute_function approach.
Introduced static methods compute_function in each affected operation module to encapsulate the core logic for executing the operation on a per-slice basis.
Updated the calling code to use the compute_function method instead of the previous partial function style

[coveralls]

coverage: 74.291% (-0.008%) from 74.299%
when pulling 450d05a on Compute_Ring_Remove-
into db14d23 on main.

[samtygier-stfc]

This is failing the check for me, if I run the compare script with options -m compare -k "ring removal" --gui it will show the baseline, new and difference. It looks like something is not working

[ashmeigh]

Closing this PR as further multithreading within the ring removal process appears unnecessary. Benchmarking reveals that the current implementation in the tomopy library already efficiently utilizes multithreading. If there are other areas where performance enhancements are needed, feel free to explore and suggest improvements.