New features + dependency/tooling clean-up

`patch-package`:
1. Has many outdated or unneeded dependencies: https://github.com/ds300/patch-package/issues/499 (@SukkaW)
2. Doesn't support monorepos: https://github.com/ds300/patch-package/issues/551 (@mdroidian)
3. Doesn't support npm's `install-strategy=linked`: https://github.com/ds300/patch-package/issues/595 (@manzoorwanijk)

It also seems like ds300 (the maintainer) isn't active enough to be merging PRs and such for these issues (no offense if you're reading this).

I'm also interested in the potential to allow people to get specific PRs before they are merged in other projects. Take for example https://github.com/colinhacks/zod/pull/5961 (a PR I recently opened). In order to patch zod for that PR right now, one has to:
1. Clone the PR, Zod's main, and the release to target
2. Useually tooling setup (`npm i`/`pnpm i`)
3. `git checkout` the release to patch
4. `git cherry-pick main..pr-branch`
5. build zod
6. copy the files resolved through package.json's `files` and `.npmignore` into `node_modules`
7. generate the patch

I feel like this could be mostly automated, so that someone could do `patch-package zod --from-pr=5961` (open to bikeshedding) to generate the patch.

I'm thinking I might fork `patch-package` to try and make this all a reality. I made this issue so hopefully the community can see it and if there's interest help out.