Cached value for the requirement coverage status is not refreshed/updated when changing the "final status precedence" flag in Xray's Test Statuses settings

 How to reproduce:

1. set Xray settings, under Test Statuses, final precedence flag to false
2. create a story A, associate it with v3.0
3. create a Test X linked with the previous story
4. from the Test issue screen, create a Test Execution TE1 for the Test, for version "v3.0" and assign it to the Test Environments: "Win10", "Windows" . Set the Test Run to "FAIL".
5. from the Test issue screen, create a Test Execution TE2 for the Test, for version "v3.0" and assign it to the Test Environments: "Linux", "RHEL6" . Leave the Test Run in "TODO".
6. from the Test issue screen, create a Test Execution TE3 for the Test, for version "v3.0" and assign it to the Test Environments: "Win7", "Windows" . Set the Test Run to "PASS".
7. create a Test Plan for version v3.0, add Test X and associate the previous Test Executions
8. change the status of Test in TE3 to FAIL
9. change the status of Test in TE1 to PASS
10. check requirement issue screen, analyzing version v3.0 within the Test Coverage section
11. set Xray settings, under Test Statuses, final precedence flag to true
12. check requirement issue screen, analyzing version v3.0 within the Test Coverage section**

Obtained results:

Expected results for the Test status, per environment,  on version v3.0:

After resetting the custom field "Requirement Status" on the story issue screen, the value of the calculated coverage for the requirement seems to be ok.