charmstore/router: generate http.StatusNotFound appropriately

This generates messages (and error codes) as expected by the API specification.
The first two, I don't think so. The third, yes, you're right - we should allow the plugged-in resolveURL function to set arbitrary status codes. Will change and add a test.