Switch from GraphQL.NET to Hot Chocolate

[RehanSaeed]

Hot Chocolate is the new hotness. I have a week of dev time coming up to get this implemented.

[lamLeX]

Hi @RehanSaeed,
Thank you for all your hard works making these templates for us.
May I have a status update of this ticket?
Would you accept a PR for this?

[RehanSaeed]

I'm currently on paternity leave and will be back in the next couple of weeks.

There were some issues with converting to Hot Chocolate v10.

• - Finish adding an example of paging with a data loader.
• - Add subscriptions.
• - If I'm using a NodeResolver, there doesn't seem to be a way to move that code to a separate class, like you can with a standard resolver. I think this is coming in v11 but need to confirm.
• - Use automatic relay input type (See Automatic Relay InputType ChilliCream/graphql-platform#773).
• - Set custom playground and voyager URL's (See Custom paths Voyager and Playground not working on AspNetCore 3.0 ChilliCream/graphql-platform#1203).

v11 fixes a lot of issues and I think makes some breaking changes. I am considering updating this PR to use the preview v11 packages. If you'd like to help, please feel free to raise a PR for this branch.

[lamLeX]

@RehanSaeed Congratulation on your new family member!!!
I'll look into your pending branch to see if I could continue with that.
Cheers

[RehanSaeed]

Fixed by #732

[RehanSaeed]

Further improvements are listed in #1022