Add support for showing fns which aren't implemented in the Type resolver fns

[orta]

Overview

type User implements Node {
    id: ID!
    slug: String!
    homepage: String!
    accountPage: String!
}

service/user.ts

const User: UserTypeResolvers = {
   homepage: ({root }) =>  "/user/" +root.slug,
   |
}

Auto-complete at the bar, should have id, slug, accountPage

Right now we only use existence of a fn in the service to indicate that there should be a type there.

IMO, we probably want UserTypeResolvers to be fully optional with all possible examples. We can still tighten the fns on the type when they are used, but we do need to be wary that there can be multiple places where a type can have resolvers added

[orta]

I've been wondering if the answer to this is maybe a separate file which would contain a version of UserTypeResolvers but be UserTypeResolversBase which contains the optional fns