Fix stats upon searching issues (#17566)

[Gusted]

Backport #17566

• Fixes a issue whereby the given chunk of issueIDs wasn't respected and
  thus the returned results where not the correct results. More specifically when the amount of returned results are above maxQueryParameters.

To reproduce this issue easily:

• Set the constant maxQueryParameters within the code to a value of 5.
• Create a new repo.
• Create more than 5 issues(I'm using 7) with the same description(e.g. Hello).
• Go to the issues tab and search for that description: Hello.
• See that amount of open issues is inaccurate and way above the correct amount.

^ This PR fixes that issue.

Their is a interesting comment above the relevant code:

gitea/models/issue.go

Lines 1502 to 1505 in bd613c7

	// If too long a list of IDs is provided, we get the statistics in
	// smaller chunks and get accumulates. Note: this could potentially
	// get us invalid results. The alternative is to insert the list of
	// ids in a temporary table and join from them.

I do think that the person writing that comment was hitting into this bug whereby the wrong issuesIDs were used in the database action and I do think it can be removed, but I'm not sure.

Screenshots(The repo had 7 issues with the description of Helo):

Before:

After: