forge--github-repository-query: Shift pagination point

Github might chose to paginate at `discussions', `discussions.comments'
or `discussions.comments.replies'.  We know that it does so at the first
of these, but not whether it also does at the latter two.  If it does,
that is a problem, which we would not be able to work around, because
(unlike `discussion') the singular variants `discussions.comment' and
`discussion.comments.reply' do not exist.

So stop limiting the number of replies to 20, and just hope that for
these edges, Github always returns all nodes, unless told otherwise.
To reduce the likelihood of making individual requests deemed to
expensive by Github, limit `discussions' to 30.  This results in more
requests and ultimately is more expensive, but that's GraphQL for you.

Closes #843.

Author: tarsius

lisp/forge-github.el

@@ -95,7 +95,7 @@
           emoji
           isAnswerable
           description)
-       (  discussions [(:edges t)
+       (  discussions [(:edges 20)
                        (:singular discussion number)
                        (orderBy ((field UPDATED_AT) (direction DESC)))]
           number
@@ -120,7 +120,7 @@
              createdAt
              updatedAt
              body
-             (  replies [(:edges 20)]
+             (  replies [(:edges t)]
                 id
                 databaseId
                 (author login)