Avoid RecursionError when using Model.set methods inside Model.read methods

[DirkEilander]

Issue addressed

Fixes #472

Explanation

I moved the initialization of the model component to the property definition.
When called the first time, we initialize the component and try to read it if in read-mode.
From the second time forward a call of the property returns the initialized component without trying to read.
Now we can use the set_ methods again inside the read_ methods like we used to do.

Checklist

• Updated tests or added new tests
• Branch is up to date with main
• Tests & pre-commit hooks pass
• Updated documentation if needed
• Updated changelog.rst if needed

Additional Notes (optional)

This could also break code downstream, if the internal properties are called (e.g. self._maps instead of self.maps). In the new implementation calling the internal static properties should be restricted to the set_ methods and the dynamic property methods only which happen in the core. Hence, an easy fix should be to replace all calls to the internal static property by the dynamic property.

[savente93]

Good to see that you added a test for this. I see nothing out of the ordinary, so if this test reproduces the problem and passes with this patch then it should be ready to merge!

[hboisgon]

Nice and more elegant way to fix model reading methods :) with this we might be changing behavior on what to expect with an empty object (eg you had to modify self.res and self.dims etc) so these changes may affect the plugins. So I think good to document the changes in the changelog.
I also discussed with @DirkEilander that the changes for Mesh will be applied in PR #412 after this has been merged.

So good to merge once the changelog is updated :)