Properly map Runtime Exceptions to 500 returns

Our RuntimeMapper currently maps RuntimeExceptions to 400 Bad Request. They should be mapped to 500 Internal Server Error.

A call to foundationdb-api earlier today received a 400 after a DB error occured. It was not immediately clear from the error what the problem was. A 500 should make this easier to understand