enhancement(dev-ex): autoapply eslint@typescript-eslint rules on downloaded components

Currently when someone installs Cedar components and they have a set of eslint@typescript-eslint rules they may break.

> I would like to use Cedar moving forward but I ran into quite a few issues while installing, mainly due to eslint@typescript-eslint rules. I had to go and make refactors through pretty much every component as a result.

- [ ] Can we make it so downloads automatically fix this? How does shadcn approach this?