middleware

PR exploring migrating to for managing this repo as discussed fixes #2001 Apart from obvious changes in actions/package.json scripts I also had to do some extra changes as the more stricter node_modules started showing a few more type issues. If you had installed node_modules with yarn previously, use to do a clean install, else stale node_modules might cause issues. I have tried my best to keep everything faithful to the original yarn version of things, but there are things I couldn't test properly like release system, but I hope we can figure out and fix broken things as soon as we find them feel free to ask about any of the changes I have made and my reasoning behind that

right now this repo is using as the package manager, which is fine but from what I can see, almost every other opensource project in the wild is using as the package manager of choice. I feel like we should also consider changing package manager, a few of the hono repos is the only reason I myself have yarn installed. There aren't any obvious reasons to change package managers, yarn is doing its job fine. But its probably better to use the common choice as then we will get all the same features and benefits as everyone else. Now if we want to switch, which package manager to switch to - https://github.com/honojs/hono and few other repos uses bun as the package manager, many other projects also make use of bun as the package manager. There were some issues with monorepo stuff last time I checked but I don't know whats the current status for that is the common and obvious choice and I am biased towards it due to my experience and almost every OSS repo using it cc @yusukebe @BarryThePenguin ref comment https://github.com/honojs/middleware/pull/2000#issuecomment-4789006603