Add an API call for retrieving the current test context stack.

We have some automated logging that runs off testing, and for diagnostics it's really useful to be able to automatically tie the spew to the test case it was emitted in. My naive hack was to just add an API call to Ginkgo that retrieves the currently running example and returns the list of containers it's in. If there's a better way I'd be happy to do that instead.