Create a lock on cached_property if not present

[tari]

This fixes #1804 (fixing breakage caused by use of undocumented implementation details of functools.cached_property) by ensuring a lock is always present on cached_property attributes, which is required to safely support setting and deleting cached values in addition to computing them on demand.

[auvipy]

thanks for the patch. do you think the change should be covered with some unit tests at least?

[auvipy]

We are hit by a test failure with python 3.12 here #1812 (comment), was thinking if this change going to fix that? or we need to update the test as well?

[tari]

thanks for the patch. do you think the change should be covered with some unit tests at least?

Yes, I should be able to add a test to verify that locks are held as needed.

We are hit by a test failure with python 3.12 here #1812 (comment), was thinking if this change going to fix that? or we need to update the test as well?

That looks like a different issue, though I didn't look at the test very closely.

[tari]

thanks for the patch. do you think the change should be covered with some unit tests at least?

Added a test that verifies the lock is acquired for all of get, set, and delete operations. I could also test that the lock is held at appropriate times, but opted not to do that since it would require doing a threading dance in the test to verify; just ensuring that the operations acquire the lock seems fine.