Add OPTIMIZE to build path

[kammce]

Adding OPTIMIZE to the build path has the sole benefit of removing the need for users to run purge everytime they want to build their application with a different optimization level. This results in a quality of life improvement due to:

1. Reduced compile times (can reuse previously generated libraries that fit the platform and the optimization level)
2. Improved expectations regarding debugging (compiling with 'g' but previously compiled library files were compiled with 3 making debugging an unexpected disaster between code that was highly optimized and code that is optimized for debugging).

This change does, consume more space user's disk based on the permutation of platforms and optimization levels used.

Additional Updates:

• At the start of the targets application, flash, and debug a "start-message" prompt will appear to give information about the target settings such as which PLATFORM, OPTIMIZE, and JTAG used.
• A bit of cleanup
• Documentation updated to reflect these changes to the makefile

[codecov[bot]]

Codecov Report

Merging #1418 (4100ca4) into master (c24d40c) will not change coverage. The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #1418   +/-   ##
======================================
  Coverage    52.8%   52.8%           
======================================
  Files          94      94           
  Lines        4506    4506           
  Branches      964     964           
======================================
  Hits         2376    2376           
  Misses       1626    1626           
  Partials      504     504           

---

Continue to review full report at Codecov.

Legend - Click here to learn more Δ = absolute <relative> (impact), ø = not affected, ? = missing data Powered by Codecov. Last update c24d40c...2dc7168. Read the comment docs.