Future of TypeGraphQL-Prisma

As you may already know, Prisma recently went through the restructuring process:
https://www.prisma.io/blog/restructure-announcement-1a9ek279du8j

The layoff also reached freelance OSS contributors, that were sponsored to work on the Prisma-ecosystem tools, like `typegraphql-prisma` itself.

What does it mean is that I won't be able anymore to develop and maintain this project in such an active way like for the last 3 years.
It's not like I won't be maintaining the project anymore but I will be able to only provide support like bug fixes or new Prisma version compatibility upgrades.

However, all the fancy features that requires more work/hours won't be implemented by me in the near future.
But I hope that the community around this project is huge and active enough that they will be implemented by Pull Request from the external contributors 😉

Thank you for all your support and let's keep `typegraphql-prisma` alive together! 💪

This issue is a project-status announcement rather than an implementation task, and it names no files, tests, or entry points. Read the announcement and surrounding discussion first; no concrete definition of done is provided, so a contributor would need a separate, scoped issue before starting work.

Written by the indexing model from the issue text.