expand:choose-next tab completion behaviour changed from fish 3.0 default

[ipwnponies]

This plugin overrides the default binding for \t from complete to expand:execute. If no expand rules match, the completion behaviour is supposed to fall back to default complete (show completion list and pager navigation for subsequent Tab).

With fish 3.0, there were some changes to handling of tab completion. This causing the expand:choose-next function to not work the same as previously. It no-ops instead of scrolling through the choices (emulating default complete behaviour).

[ipwnponies]

This seems to be caused by commandline -f complete

plugin-expand/functions/expand:execute.fish

Lines 21 to 25 in cb5e01e

	# If no replacements are available for the current token, defer to regular completion.
	if not set -q __expand_replacements[1]
	commandline -f complete
	return
	end

I tested the behaviour of complete vs. commandline -f complete, on fish 3.0.0 and fish 2.7.1:

bind \t complete
bind \cx 'commandline -f complete'

complete will show and invoke completion pager, allowing for scrolling through entries with each subsequent key press.
commandline -f complete only shows the completions, it doesn't enter the pager. Aftering entering the pager manually (using tab or arrow keys), then it will allow scrolling.