Consider dividing the crate into features for each backend and separate crates for different FFIs

This would let applications decrease the size of the library by only including what they need. I could also have a feature for Rodio support since that's probably a big part of the library size. A feature for eSpeak NG would have the additional benefit of letting non-GPL projects use it if I relicense as well, by not including eSpeak.