chore: upgrade tsconfck to 2.1.0

[christopherschroer]

Closes #103

[aleclarson]

Why is this necessary? Semver handles automatic upgrade from 2.0 to 2.1, no?

[christopherschroer]

@aleclarson Technically, yes, if you do a fresh install of vite-tsconfig-paths. However, those with existing installs of vite-tsconfig-paths and a lock file will need to uninstall/remove vite-tsconfig-paths from their project in order to remove the previous version of tsconfck from their lock file and then reinstall vite-tsconfig-paths in order to get the latest version of tsconfck. This PR makes the process of upgrading to Typescript v5 a little more streamlined for everyone

[christopherschroer]

You could also run an update on your lock file to get the latest version of tsconfck but some teams may be resistant to doing so for other reasons

[counterbeing]

PR looks pretty harmless, any chance we could get a new release? Thanks!

[aleclarson]

Released in v4.0.8