[QA] 0.58.x sync issues that still need to be verified (macOS only)

[LaurenWags]

Because it was decided that sync won't be going out enabled by default in 0.58.x, QA concentrated on verifying other issues. Because the following PR/fixes already landed in 0.58.x, we need to verify that the following have also been QA'd/verified for sync on macOS:

• Sync chain not being reset when Main device is removed Sync chain not being reset when Main device is removed #2575
• This Device is put on the wrong row This Device is put on the wrong row #2572
  * Sync chain should be reset when deleting another device with v2 spec Sync chain should be reset when deleting another device with v2 spec #2552 moved to milestone 0.60.x
• QR code/words don't display if you try to join a sync chain before starting a new one QR code/words don't display if you try to join a sync chain before starting a new one #2540
• Possible to sync the device with itself Possible to sync the device with itself #2539
• re-enabling wifi does not show sync QR code or words re-enabling wifi does not show sync QR code or words #2537
  * sometimes QR codes and words not displayed for sync sometimes QR codes and words not displayed for sync #2533 moved to milestone 0.60.x
• Removed folders re-synced only on toolbar (no folders structure), when two devices are still in sync Removed folders re-synced only on toolbar (no folders structure), when two devices are still in sync #2458
• sync does not put Android bookmarks into folders sync does not put Android bookmarks into folders #2447
• Sync should handle library/client errors Sync should handle library/client errors #2316
• Implement Sync UI Implement Sync UI #356

This issue is specific to macOS, however CCing @brave/legacy_qa please let me know if there's anything that I might have missed.

[LaurenWags]

Verified all issues passed (or have follow up issues logged) except for #2552 and #2533 which were reopened and moved to a different milestone as noted above.

[kjozwiak]

Thanks @LaurenWags 👍 Looks like #2552 and #2533 were fixed by brave/brave-core#1191 which was originally in 0.60.x but was merged into 0.59.x via brave/brave-core#1191 (comment). Moved all the issues that were mentioned in brave/brave-core#1191 into 0.59.x 👍