Refactor data_table_congruence sapply to vapply

[RobLBaker]

Basically, codefactor thinks all sapply() calls should be re-written as vapply(). I'm inclined to think it doesn't really matter much, but if anyone wants to go chase that codefactor A rating, this these are the things that need to be refactored.

CodeFactor found multiple issues:

Function "sapply" is undesirable. As an alternative, use vapply() with an appropriate FUN.VALUE= argument to obtain type-stable simplification.
R\tabular_data_congruence.R:1351
Commit RobLBaker@d3c8886
R\tabular_data_congruence.R:1070
Commit RobLBaker@d3c8886
R\tabular_data_congruence.R:1025
Commit RobLBaker@d3c8886
R\tabular_data_congruence.R:734
Commit RobLBaker@d3c8886
R\tabular_data_congruence.R:712
Commit RobLBaker@d3c8886
R\tabular_data_congruence.R:264
Commit RobLBaker@d3c8886
R\tabular_data_congruence.R:219
Commit RobLBaker@d3c8886
R\tabular_data_congruence.R:555
Commit RobLBaker@0d55e6d
R\tabular_data_congruence.R:547
Commit RobLBaker@0d55e6d
R\tabular_data_congruence.R:75
Commit RobLBaker@ee8d3ef