bug#28864: 25.3.50; next-error-no-select does select

[Juri Linkov]

>>> We can restrict to not do that when we are calling 'next-error-no-select.
>>> I think some people don't like to use this-command in such
>>> situations; alternatively, we could use `change-log-mode-hook' but the patch
>>> below is shorter and explicit.
>>
>> It's really a hack though, right? Maybe no major modes should set
>> next-error-last-buffer by itself, no matter the current command.
> That sounds better.

Please don't remove next-error-last-buffer from change-log-mode.
Actually it is legitimate use according to the documentation
of next-error-last-buffer:
"The most recent ‘next-error’ buffer.
 A buffer becomes most recent when its compilation, grep, or
 similar mode is started, or when it is used with \\[next-error]."

The problem occurred because two next-error buffer windows (*grep* and
next-error capable ChangeLog) were both visible on the selected frame,
but I believe we could fix this in the inner logic of next-error.