fix: Restore phase update to RECOMMENDED and restore negative side effects expected mutations

[howard-e]

Address #1652

This PR addresses 2 notable issues which affected older submitted reports but were part of advanced test plan versions:

1. Assertions marked as 'untestable' weren't in sync with another tester's run that marked it as 'failed'. This wasn't a problem before but now that conflicts consider these cases of untestable vs failed since fix: Show untestable vs passing/failing assertions as conflicts #1599, it has to
2. Now that AtBugs and encodedId exists on a negative side effect since feat: AtBugs for tracking known AT issues #1577, those also have to be explicitly ignored or even when the negative side effect matches, it shows up as a conflict

Apart from those, found that a created negative side effect could not be removed or updated for a Test Run page.

For reviewers:
To confirm the changes of the migration, locally I removed the markedFinalAt attribute for those TestPlanReport rows so I could easily view them in the Test Queue

[stalgiag]

Wow! This is an important catch. Thanks for thinking it through and especially for being thorough in capturing the neg side effect copying edge behaviors here