Allow Arisa to work on issues that just have been resolved

[NeunEinser]

arisa-kt/src/main/kotlin/io/github/mojira/arisa/ModuleExecutor.kt

Lines 100 to 133 in 188e542

	private fun searchIssues(
	jql: String,
	startAt: Int,
	onQueryPaginated: () -> Unit
	): List<Issue> {
	val searchResult = jiraClient
	.searchIssues(jql, "*all", "changelog", MAX_RESULTS, startAt)
	if (startAt + searchResult.max < searchResult.total)
	onQueryPaginated()
	return searchResult
	.issues
	.filter(::lastActionWasNotAResolve)
	}
	private fun lastActionWasNotAResolve(issue: Issue): Boolean {
	val latestChange = issue.changeLog.entries.lastOrNull()
	return latestChange == null ||
	latestChange.isNotATransition() ||
	latestChange.wasDoneByTheBot() ||
	latestChange.commentAfterIt(issue)
	}
	private fun ChangeLogEntry.commentAfterIt(issue: Issue) =
	(issue.comments.isNotEmpty() && issue.comments.last().updatedDate > created)
	private fun ChangeLogEntry.wasDoneByTheBot() =
	author.name == config[Arisa.Credentials.username]
	private fun ChangeLogEntry.isNotATransition() =
	!items.any { it.field == "resolution" }
	}

The filter (filter(::lastActionWasNotAResolve)) before the return statement of searchIssues currently prevents all modules from seeing issues that were resolved or reopened as the last action.

However, for most modules this is not required, and modules like the AttachmentModule should always see all issues.
Furthermore it prevents modules like requested in #145, #116, #50 and #38 to be implemented in any meaningful way.

I propose that this filter is removed from the module executor, and modules that do require it, should implement their own assertions.