Improve Sinatra and Padrino Tracing

We only offer basic/manual Sinatra and Padrino tracing.  This can be expanded to report on Sinatra specific components and internals.

'How to instrument' documentation is [here](https://github.com/appneta/oboe-ruby#sinatrapadrino).

Sample traces from a Sinatra app that uses the supported mongo library:
https://dumana.tv.appneta.com/traces/view/621A4657ED6BE53E0D2E554B55DB319E841B43D7#
https://dumana.tv.appneta.com/traces/view/579CC075CE2EFE617C4224540687387D4D67BF59#

Support should be added to hook into some of the internals of the Sinatra framework and to report controller/action type KVs.

#### Tasks

- [x] Auto insert `Oboe::Rack` middleware
- [x] Instrument template rendering
- [x] Use method profiling for partial rendering
- [x] Report Sinatra Controller/Action KVs as best fit
- [x] Report Padrino Controller/Action KVs
- [x] Auto configure Oboe.logger into Sinatra logger
- [x] Instrument and report on Streaming Responses?
- [x] Identify Padrino superset items to instrument
- [x] Instrument Padrino 'enhanced' controllers/routing
- [x] Auto-configure Padrino logger as Oboe.logger
- [x] Fix occasional missing Padrino render layer
- [x] Capture and log Sinatra exceptions
- [x] Capture and log Padrino exceptions
- [x] Update README and KB docs with updated Sinatra/Padrino instructions
- [x] Test against Modular vs. Classic Style Sinatra Apps
- [x] Test against random [open source Padrino apps](https://github.com/padrino/padrino-framework/wiki/Projects-using-Padrino)
- [x] Add automated tests for Sinatra
- [x] Add automated tests for Padrino