## Description The input_hash field on a review record entity contains criterion_config as well as information about the entity itself. The entity information is redundant, because there are fields for entity type, entity id, entity revision id (if entity supports revisions) and they are internal bundle fields. Having them in hash also makes it harder to load the review records that were done for certain configuration of the rule criteria, as when the entity has new revision the hash is also changed. It is then impossible to get why the hash was change - due to new revision or due to configuration change of the criteria. ## Tasks * [ ] Use only criteria configuration in hash method. The entity fields are attached already to the review record entity. Also external review record will not have any entity info available. * [ ] Adjust the code where necessary * [ ] Check https://git.drupalcode.org/project/ai_content_review/-/work_items/3585819 so it loads the latest review and identifies for what revision it was done, if not the default one * [ ] Check https://git.drupalcode.org/project/ai_content_review/-/work_items/3585823 to make sure that polling works correctly ## Acceptance criteria * The input hash consists only of rule criteria configuration * All the above mentioned issues are checked and necessary adjustments are provided ## Testing instructions *(added by implementor before review)* 1. Create review rule with agent based criteria and allow it to be used on content type "Page" 2. Run a review, check the input_hash field value 3. Save the node with new revision. 4. Run a review again, check that the input_hash field values is still the same. 5. Change the configuration of the rule criteria. 6. Save the node with a new revision. 7. Run a review again, check that the input_hash field is different now.