Make the useful of suggestion in node console from services.

[Score2]

Motivation

As the title says, it enables node console to directly get suggestions from the service, especially when you need to use cloudnet to debug the service.

The java sub-process started by cloudnet does not have a complete terminal environment, so it cannot directly get the service suggestions. Therefore, it can only communicate with the bridge through ChannelMessage to get suggestions.

btw, I think service suggestions are more useful on the web than on the node console, like https://github.com/docimin/cloudnet-webinterface

Modification

• Added suggestion processor ServiceCommand#suggestCommands
• Added a method SpecificCloudServiceProvider#consoleSuggestion in wrapper, Implementation in AbstractService to request suggestions from bridge.
• Fixed suggestion-processor for @Greedy processes in DefaultSuggestionProcessor

Service Platfrom Implementations

I think the feasibility and rationality of this function still need further discussion, so it is not adapted to all platforms.

• Bukkit
• BungeeCord
• Velocity
• Sponge
• Fabric
• Limbo(LOOPHP)
• Nukkit
• WaterDog
• Minestom

Result

Perfect. Like these:

Bukkit	BungeeCord	Velocity

demo video like this

Other context

Once merged, module-rest will be directly compatible with this change, further enhancing the web-interface console of service.

[Score2]

It's worth mentioning that this is a potentially destructive fix.

actually, I've tried setting the cursor in the Parser, but it obviously doesn't work for the Greedy argument, because CommandTree#L841(Incendo/cloud) restores the cursor modified in the Parser.

at least in my opinion, there is no better way to solve it properly.

[derklaro]

The biggest issue I have with the current implementation is that this introduces a dependency of the node on the bridge, which might not be installed. I think it would be better if the node provides an interface that can be implemented by modules and resolves it using the service registry. This way a module can hook into the node rather than the node hooking into the bridge.

[derklaro]

I think this method should return a future instead so that the caller can better handle errors and apply timeouts.