Enhance convert() default or unspecified parameters with preferential choices

This issue highlights the potential to enable "smarter" default or unspecified parameter decisions for `convert()` such that parameters match, for example, the storage type or align themselves in unsurprising ways. For example, if a SQLite file is provided, default parameters could align to patterns found for those data sources in order to create a better user experience. Currently, many of the defaults stem from CellProfiler CSV's, which sometimes causes unexpected challenges. Inspired by #57 .