Missing relationship fields with many in Database API find query results

[MurzNN]

1. Start the examples/blog project, fill with some data.
2. In onConnect function write two queries:

      console.log(await context.db.Post.findMany({ take: 1 }));
      console.log(await context.db.Author.findMany({ take: 1 }));

3. See in console that in Author list item the posts relationship field is missing.
   But in Post the author relationship field is present.

Will be good to describe what rule does depend on this, seems it is simple like "only relationships with many = false"?
And what about update functions - can we fill relationships with many=true or not?

So please add this nuance to the documentation here https://keystonejs.com/docs/apis/db-items

And maybe there is some option exists to load item with many relationship fields?

[MurzNN]

In context.prisma we can require needed relationship fields individually via nested reads: https://www.prisma.io/docs/concepts/components/prisma-client/relation-queries#nested-reads

      const result = await context.prisma.author.findMany({
        take: 2,
        include: {
          posts: {
            select: {
              id: true,
            },
          },
        },
      });
      console.log(result[0]);

So maybe let expose this Prisma API to Database API too?

[MurzNN]

Together with adding include and select for relationship fields, we will also give the ability to query only specific fields from database like this:

      const result = await context.db.Author.findMany({
        take: 2,
        select: {
          name: true,
        },
        include: {
          posts: {
            select: {
              id: true,
            },
          },
        },
      });

[MurzNN]

Seems we can simply add include and select arguments to current findMany() and related functions here:

keystone/packages/keystone/src/lib/core/queries/resolvers.ts

Lines 109 to 110 in 4d7483d

	export async function findMany(
	{ where, take, skip, orderBy: rawOrderBy }: FindManyArgsValue,

and pass them to runWithPrisma() directly, something like this: #7204
Is this right way to implement that?