KTI-2626: Enable cache redirector for Yarn & NPM

[fzhinkin]

kotlinx-serialization builds executed as part of the Kotlin aggregate build are failing intermittently due networking errors on the Yarn/Npm side. This PR sets up cache redirector.

Ideally, there would be a way to configure it for all projects maintained by the libraries team (such as coroutines, datetime, benchmarks, atomicfu, collections immutable) in a single place, but it seems to be tricky to implement. The main reason for that is reliance on APIs provided by KGP, those APIs depend on a particular KGP version and our libraries use different versions. Which may require slightly different approaches to configure redirection. So for now, it seems like the easiest fix would be making the proposed change.

^KTI-2626

[sandwwraith]

Looks like we need to re-generate the lock file because hashes are different now (why though?)

[fzhinkin]

@sandwwraith, that's because urls are now pointing to cache redirector.

[fzhinkin]

Discussed it elsewhere and agreed on setting up the redirector in the main branch, not only for kotlin-community/dev.

[fzhinkin]

@sandwwraith, before rebasing it all onto dev I decided to explore "make js cache redirector switchable":

• turning it off and on no longer require updating the lock file (the part I like)
• lock file patching become even more complicated (the part I don't like)

WDYT? We can still start with unconditional cache redirection and see if there will be any complaints, and only then consider this approach.

[sandwwraith]

I don't remember many complaints about cache-redirector in 'big' Kotlin (although it does have a switch). IMO we can start without one

[fzhinkin]

@sandwwraith, okay, I dropped the flag switching the redirector and rebased the branch onto dev.