Re-order NexSON-loading and tree normalization

Background: I recently added automatic resolution of sibling-only
conflicts in all candidate trees, and this is triggering some UI
refreshes in code that wasn't previously needed before tree
normalization.