fix(gitea): fetch both open and closed issues

[CirnoT]

• Fetch both closed and open issues
• Explicitly ask for both closed and open PRs (this is default but let's make sure)
• Don't include PRs when asking for issues

[rarkins]

• Fetch both closed and open issues

Can you clarify what caused you to change this? I ask partly because I want to check we are doing things consistently across all platforms, as I fixed a GitLab issues bug just now too.

[CirnoT]

I just noticed this when working on other PR.

By default Gitea returns only open issues, I don't think Renovate cares much whether it finds issue in closed state or doesn't find it (at least as far as ensureClosing goes) but my general understanding of code is that it expects to have list of both types.

Actually 'all' isn't exactly documented for ListIssues, but it is for PRs (just documentation issue, will be fixed soon) but relevant snippet is here:

	var isClosed util.OptionalBool
	switch ctx.Query("state") {
	case "closed":
		isClosed = util.OptionalBoolTrue
	case "all":
		isClosed = util.OptionalBoolNone
	default:
		isClosed = util.OptionalBoolFalse
	}

[viceice]

@rarkins I think we need this to reopen for example the config error issue.

[renovate-release]

🎉 This PR is included in version 21.18.9 🎉

The release is available on:

• GitHub release
• 21.18.9

Your semantic-release bot 📦🚀