backporting fix to stale configuration cache to v1.x.y branch

[leoromanovsky]

---

labels: mergeable

Fixes: #issue

Motivation and Context

A bug was fixed in the 3.x.y branch (435e7f0) but is effecting customers in the 1.x.y branch. We need to make a new release at 1.x.y to make it available for those not ready to upgrade to 3.

Description

Create a new release branch:

➜  python-sdk git:(heads/main) git checkout -b release/1.3.2 v1.3.1
Switched to a new branch 'release/1.3.2'

We will publish from this branch and it is the base of this PR.

Created a branch from it and cherry-picked the changes + version bump:

➜  python-sdk git:(release/1.3.2) git checkout -b cherry-pick-d663582ccabd34ec66785b1ef2c6c2709fe67300
Switched to a new branch 'cherry-pick-d663582ccabd34ec66785b1ef2c6c2709fe67300'
➜  python-sdk git:(cherry-pick-d663582ccabd34ec66785b1ef2c6c2709fe67300) git cherry-pick d663582ccabd34ec66785b1ef2c6c2709fe67300
Auto-merging eppo_client/configuration_store.py
Auto-merging test/configuration_store_test.py
[cherry-pick-d663582ccabd34ec66785b1ef2c6c2709fe67300 435e7f0] clear config store before loading new config (#30)
 Author: Sven Schmit <sven@geteppo.com>
 Date: Thu Apr 25 15:23:26 2024 -0700
 2 files changed, 14 insertions(+)

Next steps

Our github action is built to publish from main so I will perform a manual publish according to our run book.

How has this been tested?