Add server-side and test-side port retry mechanisms to handle race conditions

- Introduced a new plan to address port-in-use race conditions in both server and test environments.
- Implemented a retry mechanism with exponential backoff for binding to known ports in `LiveServer::start()`.
- Added a `respawn_with_new_port()` method in `TestServeSession` to handle transient port conflicts during tests.
- Modified `wait_to_come_online()` to retry with a new port if the server process exits due to `AddrInUse`.
- Updated `fresh_rebuild_read()` to include port retry logic, enhancing robustness against port conflicts.

These changes aim to improve the reliability of server and test interactions by mitigating race conditions related to port usage.

plugin/src/App/Components/TableDiffVisualizer/Dictionary.lua

@@ -7,6 +7,7 @@ local Roact = require(Packages.Roact)
 local Timer = require(Plugin.Timer)
 local Assets = require(Plugin.Assets)
 local Theme = require(Plugin.App.Theme)
+local trueEquals = require(Plugin.Reconciler.trueEquals)
 
 local ScrollingFrame = require(Plugin.App.Components.ScrollingFrame)
 local DisplayValue = require(Plugin.App.Components.PatchVisualizer.DisplayValue)
@@ -35,8 +36,7 @@ function Dictionary:calculateDiff()
 				key = key,
 				patchType = "Remove",
 			})
-		elseif newValue ~= oldValue then
-			-- Note: should this do some sort of deep comparison for various types?
+		elseif not trueEquals(oldValue, newValue) then
 			table.insert(diff, {
 				key = key,
 				patchType = "Edit",