Warn when duplicate field labels are detected

[ezraporter]

Description

This PR implements a warning when REDCapTidieR detects a radio or dropdown field with duplicated labels. It also fixes the cryptic error noted in #89 (comment)

Proposed Changes

List changes below in bullet format:

• Create check_parsed_labels() check function and call it in multi_choice_to_labels() after the labels are parsed
  • I thought about doing this within parse_labels() but this function gets called multiple times
• Add a field with duplicate labels to the classic test REDCap and suppressWarnings() where necessary throughout the tests

Screenshots
Example warning:

Issue Addressed

closes #89

PR Checklist

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

• New/revised functions have associated tests
• New/revised functions that update downstream outputs have associated static testing files (.RDS) updated under inst/testdata/create_test_data.R
• New tests that make API calls use httptest::with_mock_api and any new mocks were added to tests/testthat/fixtures/create_httptest_mocks.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_dev_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

[rsh52]

Overall this looks great, a few comments and suggestions related to tightening up naming conventions/documentation open to discussion.

[ezraporter]

Made the following updates:

• Added a return_stripped_text_flag parameter to parse_labels() to have it optionally return a flag indicating whether we changed the labels by stripping text
  • Minor refactoring of parse_labels() to achieve this
• Pass that flag to check_parsed_labels() to determine whether we should add the note about HTML
• Added a check to check_parsed_labels() to warn if any labels are blank ("")

[rsh52]

This is definitely starting to get complicated, but I think it looks good and I can generally follow the qualifier variables/arguments informing what checks we expect to fire off.

The tests also look good, we just want to be mindful that some of the test cases we're addressing that prompted these functions are spread across smaller tests.