fix(cli): Service generator supports relations

[dthyresson]

This PR address an issue when using yarn rw g service independently vs having ti be called by yarn rw g sdl or yarn rw g scaffold.

When using yarn rw g service, the model's relations were not correctly determined. For the sdl generator, relations are determined and then passed as an argument to the service generator; however, if you run just the service generator, the relations were always [].

Thus, for the test fixture model schema:

model User {
  id       Int           @id @default(autoincrement())
  name     String?
  email    String        @unique
  isAdmin  Boolean       @default(false)
  profiles UserProfile[]
  transactions Transaction[]
}

A user has two relations: a UserProfile and transactions.

Without the fix, the following is missing from the user service:

export const User = {
  profiles: (_obj, { root }) => {
    return db.user.findUnique({ where: { id: root?.id } }).profiles()
  },
  transactions: (_obj, { root }) => {
    return db.user.findUnique({ where: { id: root?.id } }).transactions()
  },
}

Fixing because when using experimental sdlCodegen, I write the SDL manually and then generate the service. I also will have a custom template for the sdlCogen pattern, but my template failed because it didn't get the the relations to properly build out the service according to my template.

This is why this PR also bumps the sdl-codegen package.