Feature/mongo objectid

[eric-burel]

• [X] Introduce a GraphqlObjectId scalar that converts to _id
• [X] Demo enabling this scalar in Vulcan Next
• [x] Test on _id
• [ ] Test on userId with "owners"
• [ ] Test owners permission
• [ ] Test on a relation field
• [x] Test inside filters: we probably must create a new "ObjectIdSelector" type?
• [x] Drop dependency to Mongoose when unwanted: create a true "mongo connector" that returns a Mongo collection (and figure how to force string ids?), remove dependency to Mongoose in Vulcan Next, then separate packages in a future version for people who still want mongo
• [x] Document using GraphqlObjectId typename everytime we use an _id
• [x] Make the connector conversion to string an option => it should not be needed anymore? since the graphql scalar is supposed to handle the conversions correctly. We might want to double check if multi query still work ok, especially for resolved fields.
• [x] Document both using strings and ObjectId
• [ ] Test string id in state of with new option

If it doesn't work as expected, we can drop support for ObjectId and impose users to use strings instead. This PR would still be relevant anyway as it improves the graphql schema generation system.

@closes https://github.com/VulcanJS/vulcan-next/issues/162 @closes https://github.com/VulcanJS/vulcan-npm/issues/63

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
vulcan-docs	✅ Ready (Inspect)	Visit Preview	Jun 23, 2022 at 6:55PM (UTC)
vulcan-npm	✅ Ready (Inspect)	Visit Preview	Jun 23, 2022 at 6:55PM (UTC)