Support for more waypoint types

[i25052i]

Description

We now support several additional waypoint-based commands and the ability to pass in parameters to them.

Resolves #66 & #68

Type of change

What types of changes does your code introduce to this project? Put an x in the boxes that apply

• [ ] Bugfix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] Documentation Update (if none of the other choices apply)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes.

• [ ] Test A
• [ ] Test B

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. This is simply a reminder of what we are going to look for before merging your code.

• [ ] My code follows the style guidelines of this project
• [ ] I have performed a self-review of my code
• [ ] I have commented my code, particularly in hard-to-understand areas
• [ ] I have made corresponding changes to the documentation
• [ ] My changes generate no new warnings
• [ ] I have added tests that prove my fix is effective or that my feature works
• [ ] New and existing unit tests pass locally with my changes
• [ ] Any dependent changes have been merged and published in downstream modules

[i25052i]

TODO list:

• GET /queue should return the specific waypoint types
• add support for DO_SET_SPEED
• Revise how we ingest waypoints/commands in POST /queue - certain commands have different parameters/fields and we don't want to be reusing the lat/long/alt fields.