Expose REDCapR col_types

[rsh52]

Description

This PR seeks to allow users access to the col_types parameter. This will help with tackling cases where REDCapR/readr do not correctly guess the data type of outputs. This only seems to happen in niche instances, and was brought to our attention in the example of a radio button/single selection field for M/F/Unk where all entered data was "F", resulting in an incorrect application of T/F for the field type.

Proposed Changes

List changes below in bullet format:

• Expose col_types in read_redcap and downstream in redcap_read_oneshot
• Add col_types param and section roxygen documentation
• Add additional message to check_extra_field_values_message() which we may want to break out in future [FEATURE] Expand checks to look for mismatches between metadata and raw data #237
• Minor changes to linting and styling
• Update version and NEWS

Issue Addressed

Closes #236

PR Checklist

Before submitting this PR, please check and verify below that the submission meets the below criteria:

• [NA] New/revised functions have associated tests
  • Assumed unnecessary since this is a core feature of REDCapR
• [NA] New/revised functions that update downstream outputs have associated static testing files (.RDS) updated under inst/testdata/create_test_data.R
• New/revised functions use appropriate naming conventions
• New/revised functions don't repeat code
• Code changes are less than 250 lines total
• Issues linked to the PR using GitHub's list of keywords
• The appropriate reviewer is assigned to the PR
• The appropriate developers are assigned to the PR
• Pre-release package version incremented using usethis::use_version()

Code Review

This section to be used by the reviewer and developers during Code Review after PR submission

Code Review Checklist

• I checked that new files follow naming conventions and are in the right place
• I checked that documentation is complete, clear, and without typos
• I added/edited comments to explain "why" not "how"
• I checked that all new variable and function names follow naming conventions
• I checked that new tests have been written for key business logic and/or bugs that this PR fixes
• I checked that new tests address important edge cases

---

• To see the specific tasks where the Asana app for GitHub is being used, see below:
  • https://app.asana.com/0/0/1212592521610072

[ezraporter]

One suggested change to the docs if you want it but I support merging as is too. Thanks for all the additional clean up as well!

[rsh52]

Awesome, thanks!