Allow customize interceptors

[mateusduboli]

Context

We have some problems with the raise interceptor that it, in conjunction with the way martian defines the interceptor stack, will always log the exception on stderr.

Explaining in more detail:

• The interceptors.raise code will throw if there is a non 200 status.
• That exception is thrown over the tripod stack and will be raised to the tripod.context/execute call.
• Martian executes the interceptor stack using the callback from http-kit.client/request
• Any exception thrown there will be logged to stderr by httpkit, which seems to me like a problem and should not be happening, thus there is a ticket about it Exceptions on callbacks are always logged to stderr http-kit/http-kit#518.

The proposed solution by the developers is to catch such exceptions before, which seems to be a good option, considering that what we are doing on OUR code is to use http status as control flow and exceptions are not actually a good driver for this.

The main issue here, is that with these exceptions always being logged on stderr causes our monitoring to be hectic as we should keep monitoring for problems there and ignoring stack traces seems to be dangerous in this situation.

Impact

I've checked the usages of the kubernetes-api.core namespace, and there does not seems to be any usage of the :interceptor parameter, even it being a breaking change, it will not have impact on our codebase.

Changelog

• Remove usage o :refer :all in tests
• Allow for the :interceptor parameter to override all the default interceptors of the client.