I've been thinking of ideas for the library API that can provide more powerful functionality, while also reducing how much of the bat internals are exposed. Feedback would be appreciated.

Most of the current implementation for Decoration is fine for a public API, but we should remove the parameter that is passing around the internal InteractivePrinter struct.

If we choose to implement input source properties as described in #729, this could be easily fixed by using the HashMap<&'static str, Any> with builder solution.

I would also suggest that we move the git changes decoration into its own cargo feature (git-decorations maybe?), and possibly split off each decoration into its own file.