The GitHub mirrow has been temporarily out-of-sync since past Wednesday
November 17th which, even though they run a couple of manual syncs in
the past days, is causing trouble for us to work on rebases because we
can't fetch the right tags from the mirror.
This change changes the URL in package.json to point to the upstream
repository and makes the necessary changes to npm run sync so that
the gclient and git configurations get updated to it.
According to the upstream bug at https://crbug.com/1272797, this
situation should be fixed soon as it's been treated as high prio,
but we can't depend on that to be able to update to newer tags, so
we'd better make this change now, and then maybe return to using the
GitHub mirror later on when the situation is fixed, if needed.
- Removed npm-force-resolutions due to issues with transient dependency versions with storybook's builder-webpack4 not getting the correct version of terser-webpack-plugin
- Updated storybook minor version to remove the audit issue that npm-force-resolutions was fixing.
As reported in https://github.com/brave/brave-browser/issues/20501,
the NTP was making outbound requests to ftx.com at startup without
user opt-in, and the network-audit didn't catch that case because
it was NOT loading a NTP as part of the different checks it does
at BraveNetworkAuditTest.BasicTests.
This patch adds explicit test coverage for that case by loading
brave://newtab and waiting 5 minutes, like with the other checks.
Resolves https://github.com/brave/brave-browser/issues/20504
Mario Sanchez Prada