Change rule_evaluations upsert to set migrated to true

[dmjb]

This query is always called after an upsert into the evaluation history table, so migrated should always be set to true. Due to the lack of the update in the ON CONFLICT DO UPDATE clause, we ran into a situation where unmigrated rows in rule_evaluations were being implicitly migrated by the policy migration (i.e. the code was creating a corresponding row in evaluation_rule_entities) but the migrated flag was still set to false. The migration script would then attempt to copy the data to the evaluation_rule_entities table, which would error out because the data for that rule/entity pair already existed.

Summary

Provide a brief overview of the changes and the issue being addressed.
Explain the rationale and any background necessary for understanding the changes.
List dependencies required by this change, if any.

Fixes #(related issue)

Change Type

Mark the type of change your PR introduces:

• Bug fix (resolves an issue without affecting existing features)
• Feature (adds new functionality without breaking changes)
• Breaking change (may impact existing functionalities or require documentation updates)
• Documentation (updates or additions to documentation)
• Refactoring or test improvements (no bug fixes or new functionality)

Testing

Outline how the changes were tested, including steps to reproduce and any relevant configurations.
Attach screenshots if helpful.

Review Checklist:

• Reviewed my own code for quality and clarity.
• Added comments to complex or tricky code sections.
• Updated any affected documentation.
• Included tests that validate the fix or feature.
• Checked that related changes are merged.

[dmjb]

Red build is caused by the known OpenFGA CVE issue, and does not relate to the changes here.

[coveralls]

coverage: 53.891% (-0.01%) from 53.904%
when pulling 326adc7 on rule-eval-upsert-migrate
into 0d2c3b8 on main.