Refactor coloring in compiler

[wooster0]

This:

• Resolves unnecessary colorizing complexity in the compiler.
  Originally I just wanted to fix that when you do '', that the did-you-mean in the error is colored in bold yellow (currently it's not) but it turned out to be actually quite difficult to retrieve the @color value from the Compiler (whether --no-color has been passed or not) from this spot in the lexer.
  So now at the beginning of a compilation, Colorize.enabled is simply used to turn colors off when --no-color has been passed. Which is much simpler than having to define a colorize method first and then having to figure out how to even retrieve the color value from the compiler. Now strings can be colored wherever you want just like you would in your own code without colorize helper methods.
• Removes 2 unnecessary "colorize" requires.
• Fixes some did-you-means or other helpful hints not being colored in bold yellow in multiple places.
• For example Time.new(seconds: 0) results in the error
  
  with the last item not being colored in bold/white (or more specifically with the items after the (trying this one) not being colored in bold/white). That's fixed as well.

[wooster0]

Phew CI finally passes! That took way too long.

[wooster0]

#4499 looks much better than this, I'll close this and perhaps do an extra PR someday with some tiny things of this that #4499 doesn't have, after #4499 is merged.