Complete revamp

[WhyAsh5114]

Moving to multi-class approach

To support relations, we can't re-use a base class for all the models, at least not with my current TypeScript skills.

Performance issues

Moving to individual classes for each model, this does take up quite some time to generate (~2s) even for small schemas, maybe this is due to using Node to write files, or I wrote terrible code (probably I wrote terrible code), but its something I'm willing to sacrifice for now till the complete API with relations and schema features can be implemented through IDB.

API progress

Model queries

• findUnique()
• findUniqueOrThrow()
• findFirst()
• findFirstOrThrow()
• findMany()
• create()
• update()
• upsert()
• delete()
• createMany()
• createManyAndReturn()
• updateMany()
• deleteMany()
• count()
• aggregate()
• groupBy()
  findRaw()
  aggreagateRaw()

Model query options

• select
• include
• omit (Preview)
  relationLoadStrategy (Preview)
• where
• orderBy
• distinct

Nested queries

• create
• createMany
• set
• connect
• connectOrCreate
• disconnect
• update
• upsert
• delete
• updateMany
• deleteMany

Filter conditions and operators

• equals
• not
• in
• notIn
• lt
• lte
• gt
• gte
• contains
• search
• mode
• startsWith
• endsWith
• AND
• OR
• NOT

Relation filters

• some
• every
• none
• is
• isNot

Scalar list methods

• set
• push
• unset

Scalar list filters

• Remarks
• has
• hasEvery
• hasSome
• isEmpty
• isSet
• equals

Atomic number operations

• Operators
• Remarks
• Examples