Ak/check derived task ids/189

[annakrystalli]

Instead of reviewing I've just gone ahead and made a PR with my suggestions.

This PR build on #190 but introduces the following changes:

• Instead of converting all but the value column to character, it expects an all character tbl and converts just the value column to numeric. This is how the original test was setup and the conversion of value to numeric was already happening in check_values_ascending() on the subset of relevant rows for the check.
• I've updated the function documentation to reflect the above input change.
• To avoid unnecessary computations, I've taken the output types to check from the tbl itself instead of the config. That way we do not spend time creating expanded grids for optional output types in the config that do not exist in the data.
• I also went ahead and split the check by output type for maximum memory efficiency.
• I reverted the input to the check in validate_model_data() to be the tbl_chr version of the data. This exists in the function environment as a number of checks depend on the all character version of the model output data.
• I corrected the tests to reflect this input expectation. I also removed unnecessary hubValidations namespace specifications
• I added a test that checks derived task IDs are indeed ignored.

I've tested locally and all tests pass but will be good to run the tests in your PR once merged in before merging into main

[zkamvar]

Thank you for the improvements, Anna! It all looks good with two things that can be tweaked:

1. the value column still needs to be converted to numeric
2. replacing a map over a single-element list with calling the function directly (see comment)

Additionally, should the function signature for check_tbl_value_col_ascending() be tbl_chr instead of tbl so that it's clear it expects a character-only tbl?

[annakrystalli]

Additionally, should the function signature for check_tbl_value_col_ascending() be tbl_chr instead of tbl so that it's clear it expects a character-only tbl?

This is a good idea but should be applied throughout on all functions that require tbl_chr. For now we have it in the documentation of check_tbl_value_col_ascending() that this is the required input to tbl so best to just open a new issue to change tbl to tbl_chr on all affected check functions.