Instead of dealing with bundles of Vec<u8> each file sink and client
will be paired over any type that can be turned into bytes.

…ost traits

To keep from dealing with Vec<u8> and String auto implementations for
prost::Message that disallows using a file sync with anything but a
prost::Message.

We're going to follow the other Msg* trait conventions where we
implement them only for the types we are using.

This allows someone to make a file sync for whatever type they may have,
and convenience for proto types we write reports about.

The abstraction comes in two parts.

The first we can get a file sink from a type if it implements the
FileSinkWrite trait.

The second is a type being able to be written to a file sink if it can
be turned into bytes.

This separates the convenience from the actual functionality.

this allows us to attach the metric name to the file type
implementation, and only have to pass in the calling crate for the
prefix.

FileSinks are really only created once, and there are not so many of
them that owning a string introduces a crazy amount of overhead.

The FileSinkWrite trait is a convenience method for creating file sinks,
but it should not be tied to being able to use a file sink. The only
requirement for that is being able to turn your message into bytes.

This is a specialized helper function, every crate using it was only
using these two options. We can provide the base functionality with a
single option.

Ideally the Builder would be updated to take some sort of enum for the
commit type as it doesn't make a lot of sense to auto_commit on every
write _and_ roll the file at a certain interval.

- include new verified mapper code
- update deps
- fix botched rebase conflicts

Taking a static string allows FileSinkWriteExt to be implemented by
users outside the oracles codebase, and starts the journey of moving
away from the FileType enum.