create a class to be the common formatter

Plan is to load all of the templates and dynamically create methods to handle the different template options.
rename templates to formats

formats are for individual posts while templates are for pages (collections of posts)
use the term formats instead of templates in class
add raw formatter to test data

now the tests should pass
begin testing the format method
make first format test past
create and test error hierarchy

create namespaces errors to avoid conflicts with other libraries
begin incorporating error hierarchy
ensure that valid input does not crash format
ensure that raw format is processed correctly
remove formatters

they have been migrated to the content repository
use the formats method where it makes sense
use dynamic formatter method in index
modify runner to match the new expectations of index initializer
simplify formatted_output method
rename file to match new purpose

Originally `formatters` contained 4 different formatters, now there is just one class. Hence the singular file name.