Wrap types so we don't have to re-export owo_colors

[jssblck]

Hey there! I read #109, and understand why owo_colors is re-exported, but the original author is quite correct that it makes completions really noisy. They were using IntelliJ, but I'm using VS Code with Rust Analyzer and it has this same issue.

Would you accept a PR that newtype-wraps all the owo_colors bits so that it doesn't have to be re-exported?

I'm envisioning, for example:

• color_eyre::config::Theme::file accepts owo_colors::Style today.
• We could make it instead accept a new trait, e.g. impl color_eyre::config::Style, which is automatically implemented by owo_colors::Style.

And so on.

[belakm]

I second this 👍 developer experience with unrelated auto-suggestions is unpleasant

the alternative i took at the moment is going back to eyre crate

[FlareFlo]

Alternatively, the re-export could be feature gated, optionally disabling it when unneeded.