Allow profiling of queries via the API

It is currently possible to profile queries via the go `Describe()` function but it will nice to have it available from the API.

Here is an example of Neo4J `profile` command. I think we should first expose it to the console and maybe later on to the web interface.

Start with the Go Describe() function and trace how query profiling is exposed through the existing API and console entry points. Define the API response and console behavior for profiling a query, then verify that profiling works through the API as well as the console; the issue does not name specific files or tests.

Written by the indexing model from the issue text.