Future remote API enhancements

[Amethyst-Sysadmin]

Potential enhancements to Howl's remote API to make life easier for developers that require some additional work to implement.

• The endpoints that load content into the player should have a parameter that makes playback start immediately rather than requiring a separate request to start the player.
• When loading HWL files the caller should be able to set a parameter to specify whether they will loop or not (maybe for funscripts as well to keep those endpoints mirrored, although that is less useful).
• As discussed in I added an automatic ramp-up feature for power intensity，i hope it can merge in master branch #23 it would be helpful if there was a function to preload an HWL file into memory and associate it with a string key. Developers could then call an endpoint like /play("shoot") or /play("jump") to easily and quickly play the patterns they preloaded. This would be handy for anything event based like tying playback to actions in a game.

[Amethyst-Sysadmin]

Added the first two prior to the initial API release.