🐛Fixes CLI hanging in commands calling 'make.exe'

[BennyBot]

Summary:

Previously: If 'make.exe' wasn't found, the 'EchoPipes' used to communicate the build status to the user would hang.
Changes: Used try/except on the 'pros make' command and 'pros build-compile-commands' commands. If an exception is thrown when running 'make.exe', the program will close the 'EchoPipe' class(es), print an error message to the screen, print a warning IF the pros toolchain is not found, and then exit.

Motivation:

The hanging terminal got on my nerves while trying to get the toolchain installed correctly on my windows pc.

References (optional):

This may be related to #83, as calling 'make.exe' through 'build-compile-commands' would hang the CLI if any exception was thrown during that subprocess.

Test Plan:

Ran both 'pros make' and 'pros build-compile-commands' with and without the toolchain environmental variable. Acts normally if 'make.exe' is there, and exits without hanging if an error is thrown during the calling of 'make.exe'
Screenshot of non-hanging terminal after both commands fail shown below.

[BennyBot]

'pros make' and 'pros build-compile-commands' commands WITH 'PROS_TOOLCHAIN' in environmental variables.

'pros make' and 'pros build-compile-commands' commands WITHOUT 'PROS_TOOLCHAIN' in environmental variables.

[HotelCalifornia]

@BennyBot one further test: try to build a project with no PROS_TOOLCHAIN variable but the toolchain folder is on PATH

[BennyBot]

'pros make' and 'pros build-compile-commands' commands without 'PROS_TOOLCHAIN' in environmental variables but the toolchain in PATH.

I made it only give the warning that pros toolchain was not detected if the subprocess threw an exception, because if someone went through the lengths to not have the PROS_TOOLCHAIN env. variable but still have it work then they probably wouldn't want a warning whenever they built. I could move this warning outside of the try/except block if you think it should warn every time.

LGTM