Create profiling for Scheme and JavaScript code

[jcubic]

Check which Scheme function or macro is called the most times during the unit test run.

Optimizing the most used functions or macros can make a difference in speed.

• Find or create a new tool for profiling
• Run profiling on Scheme code
• Run profiling on JavaScript code

[jcubic]

Key finding:

• Line 11667: evaluate function - main interpreter (18.6% CPU)
• Line 11480: evaluate_macro function - macro expansion (9.8% CPU)
• Line 11398: resolve_promises function - traverses trees for promises
• Line 11401: traverse nested function - the actual hot loop (2.1% CPU)
• Line 1947: unpromise function
• Line 1966: unpromise_array function
• Line 5628: loop in let/let*/letrec (7.4% CPU)