[Behaviours/3] Implement NavigateTo Skill

Blocked by #399 (closed), #468, #469 (closed)

BT Node/Branch Implementation Ticket

• Implement the given M-STP Behaviour using the given structure designed during Agent meetings.
• Create unit tests/agent tests to test your given mechanic/skill/tactic/play to ensure that it works correctly.
• If you are working on a higher level STP relying on lower mechanics, leave stubs for the required Mechanic, Skill, or Tactic.
• DO NOT SUBMIT YOUR PR UNTIL THE LOWER LEVEL M-ST IS MADE! Wait for the person working on that node and implement it. Feel free to work on another ticket if you are blocked, but ensure to come back to this one when it is available.

Acceptance Criteria

• Checks Passed
• Peer reviewed at least once
• Demo'd with a screen capture in PR, or shown to @dayvidpham

Dependencies

Should finish these tickets before starting this one.

• the NavigateTo stub in #399 (closed)
• for-loop control into new ticket #468
• interacting with PathPlanner::GetPath as mechanic #469 (closed)

Tied to #343 (closed) and #344. View those tickets for more information on how to implement the BT Node.