Refactoring logging functions / make the error messages more closely match gccs output

[jaredponn]

This PR:

• Refactored all logging (logError and logInfo functions (from lambda-buffers-frontend and lambda-buffers-codegen) to reuse the logging functions in lambda-buffers-compiler since lambda-buffers-compiler is an existing dependency of both lambda-buffers-frontend and lambda-buffers-codegen
• Change error / info messages to be dumped to stderr instead of stdout (this is more aligned with other compilers' behaviors)
• Shuffled error messages to more closely follow what gcc outputs e.g.

  $ lbf-prelude-to-haskell DoesNotExist.lbf
  DoesNotExist.lbf: error: the provided module file DoesNotExist.lbf doesn't exist
  
  $ cat TEST.lbf
  module TEST
  
  import Prelude (Eq, Json, Maybe, Either, List, Integer)
  
  derive Eq What
  $ lbf-prelude-to-haskell TEST.lbf
  TEST.lbf:5.11-5.15: error: [module TEST] type What not found in the module's scope Either Integer List Maybe Prelude.Either Prelude.Integer Prelude.List Prelude.Maybe
  
  $ cat TEST.lbf
  module TEST
  
  import Prelude (Eq, Json, Maybe, Either, List, Integer)
  
  prod What = (Integer
  derive Eq What
  
  $ lbf-prelude-to-haskell TEST.lbf
  TEST.lbf:6.7: error:
  unexpected keyword
  expecting s-expression
  

[bladyjoker]

This looks great!

I left a comment about extras/lambda-buffers-utils to keep the compilation level separation. Let me know if that works

[bladyjoker]

Thank youuuu!!!

[szg251]

I thought I reviewed this earlier...

[jaredponn]

I'll merge this since it seems we've addressed all PR feedback :P