Improve Tuning CLI - Up Arrow For Previous Command

[CodeMyGame1]

Problem: Currently, the tuning CLI appears similar to a normal bash terminal, accepting a command, and then showing the corresponding output. However, similar to a bash terminal, there are commands in the tuning CLI that will inevitably be run multiple times in succesion (such as run, which runs the test autons). It's very tedious to keep typing these commands again and again Significance: Similar to a bash terminal, if there was functionality that allowed you to "fetch" previous commands by repeatedly pressing the up arrow, it would significantly decrease tuning time! Solution: I propose that...

• as part of the CLI tuning functions (see gh-3), include an array that stores a history of the last ten commands that have been called
• we implement a function that detects up arrows, but prevents them from being "printed" to terminal (i.e. preventing the cursor from moving up one line, which would mess up the command that's currently being typed)
• connect the up arrow function to the history array, fetching previous commands up until the limit of past 10 commands

NOTE: keep in mind gh-3 when implementing a fix to this issue!

[CodeMyGame1]

In addition, we could colorize different commands as they are typed in, providing additional confirmation to the user that they are running the command they want to (see gh-5)

[CodeMyGame1]

prevents them from being "printed" to terminal (i.e. preventing the cursor from moving up one line, which would mess up the command that's currently being typed)

In addition to this issue, I found another issue while debugging the tuning CLI: the delete key moves the cursor beyond the entered command, into the enter command> part of the line, messing up the inputted command by polluting it with escape strings for the delete key. Disallow the user from deleting beyond whatever command input they have typed in (we will probably need to handle delete keypresses asynchronously)