feat(ci): refactor updateProjectReferences

[Lemonexe]

Description

As discovered in #17234, the updateProjectReferences.ts script does not treat tsconfig.ts & tsconfig.lib.ts consistently.

Currently you can push incomplete tsconfig.lib.json to master; it will pass CI, because yarn verify-project-references throws only on tsconfig.json. But yarn update-project-references modifies also tsconfig.lib.json.
This is inconsistent, yarn verify-project-references should throw if there are any changes that would be modified by yarn update-project-references.

➡️ fixed it, and reorganized the code while doing that; I hope it will be easier to read now 🙂

QA

I tried:

• yarn verify-project-references passes ✔️
• yarn refs passes with no change ✔️
• In some packages, editing either (tsconfig.ts, tsconfig.lib.ts or both), by either (adding line, removing line, swapping lines or removing references altogether) and then first running:
  • yarn verify-project-references to make sure it throws ✔️
  • then yarn refs to make sure it corrects to original state (no git diff) ✔️
• Removing tsconfig.ts:
  • yarn verify-project-references throws ✔️
  • yarn refs recreates it, but not necessarily to the same state (the defaultConfig has some different fields) 🤷
• Removing tsconfig.lib.ts: both scripts pass, no change ✔️

[Nodonisko]

LGTM! Thanks for fixing it 👍 🚀