On temporarily re-opening next-transpile-modules

[martpie]

I'll keep it short: one edgecase of next-transpile-modules it not covered by Next.js 13's transpilePackages, a few people cannot use the official solution, and require their packages to not be deprecated (corporate policies yadi yadi yada).

• I removed the deprecation on next-transpile-modules and "un-archived" the repo
• I closed all the previously open issues to have the issues as a way to close the gap with the official solution, not to support next-transpile-modules as a competing solution (it's not!)
• ... but I don't plan to work on it (or max, on a best-effort basis)
• PRs with fixes and improvements are welcome and I'll help review them

Eventually...

... it could be a good idea to have next-transpile-modules@vNext as a bridge between current next-transpile-modules and transpilePackages, so we would remove most of the code of next-transpile-modules (now obsolete, and native in Next.js), and just make sure next-transpile-modules overload transpilesPackages to make sure all existing setups work, until official fixes land in Next.js.

I said it and will repeat it again: if you want to invest time closing this gap: work directly on Next.js and submit a PR there. The only advantage of next-transpile-modules is speed of release, but this won't be last forever, and there will be a time I will retire this package for good.