Implement LoggerType#dump

[david942j]

Implement #62

libc = 0xdead000
stack = 0xbeef000
log.dump libc.hex, stack.hex
# [DUMP] libc.hex = "0xdead000", stack.hex = "0xbeef000"

Hacky methods are used:

1. Get the source code from file (using gem method_source)
2. Parse the source code to Sexp (using ruby_parser)
3. Traverse the sexp to find the block/arguments when calling dump
4. Convert the sexp of block/arguments back to Ruby code (using gem ruby2ruby)
5. Show the result

Therefore, some unusual usages will fail, such as:

• log.dump(&a_proc) # nil will be logged
• log.dump { 1 }; log.dump { 2 } # will log 1 two times

Two new dependencies are added:

• method_source
• ruby2ruby

---

This change is 

[david942j]

to find

[hanhanW]

will be parsed by using +ruby_parser+

[hanhanW]

Support log.dump(x+y) instead of log.dump('x+y') would have better user experience.

[hanhanW]