365 potentially remove interactionvaluesvalues

[Advueu963]

This pull request addresses #365 and #385 by changing InteractionValues.values and InteractionValues.interaction_lookup them into properties. Introducing InteractionValues.interactions as the main part working with interactions.
We remove finalize_computed_interactions and incorporate it into the __init__ of InteractionValues.

Removal of finalize_computed_interactions:

• Updated all approximate methods in various approximator modules (owen.py, stratified.py, montecarlo/_base.py, permutation/sii.py, permutation/stii.py, permutation/sv.py, regression/_base.py, sparse/_base.py) to directly return InteractionValues with the target_index property included. This eliminates the need for the finalize_computed_interactions function. [1] [2] [3] [4] [5] [6] [7] [8]

• Updated the explain_function in tabular.py and tree/explainer.py to replace calls to finalize_computed_interactions with direct instantiation of InteractionValues. [1] [2]

Simplification of imports:

• Removed finalize_computed_interactions from imports in all affected files, as it is no longer used. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11]

These changes improve the maintainability of the code by reducing complexity and removing unnecessary dependencies.

[mmschlk]

This is amazing ... but we really gotta be careful integrating this haha 😂

[mmschlk]

We could add this logic actually also to our game class ... I don't see if there is something which speaks against this.