Upgrade Dependencies, DataProvider migration and is/isnot handling

[BeardInASuit]

Maybe it is a breaking change since LegacyDataProvider is migrated to DataProvider

• Upgrade dependencies to Prisma 5 and React 18
• Migrate LegacyDataprovider to DataProvider
• Handle 'is', 'isNot' on top of 'Some' in filters

[macrozone]

@BeardInASuit

i did not have time to release the "beta" version yet, but that has support for newer prisma versions.

https://github.com/panter/ra-data-prisma/tree/beta

The dataprovider itself has not direclty something to do with prisma, its just that the graphl api is similar.

Initially the api is derived from nexus-plugin-prisma, which is deprecated for some time.

in the beta branch a forked version of nexus-plugin-prisma is used. that also generates slightly different queries in some edge cases (i think sorting of related records).

So it would be best to target further improvements on the beta branch, so if possible could you:

• rebase with the beta branch
• the "Migrate LegacyDataprovider to DataProvider" is welcomed, but i think its best to be a separate commit, since its just refactoring
• for the additional "is" and "isNot" filters, could you add tests? not sure if they are now also supported in the beta branch. I am also not sure whether both typegraphql and nexus support this?