Improve `REDCapR` error messages

[ezraporter]

Description

This PR improves error messages produced by try_redcapr() in 2 scenarios:

1. The REDCapR operation returns with success == FALSE but doesn't error

In these cases we check for a few common error codes

https://github.com/CHOP-CGTInformatics/REDCapTidieR/blob/fe147b4e476c496f5ded1dfc54b4a66601ce53fc/R/utils.R#L641-L657

and otherwise issue a generic "unexpected error" message with our bug report link. This hides information REDCapR may have returned in outcome_message.

This PR includes the contents of outcome_message in the error. See screenshot 1.

2. REDCapR returns success == FALSE due to a deleted project

This is the situation that instigated investigating scenario 1. I added an explicit check for this error message to the error code checks above.

Proposed Changes

• Add the content of outcome_message as the parent in abort when handling an unexpected error
• Add explicit check for deleted projects

Screenshots New unexpected error message: (Note that this won't actually ever appear because we added the explicit check for this case)

New deleted project error message:

PR Checklist

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

• [x] New/revised functions have associated tests
• [x] New/revised functions that update downstream outputs have associated static testing files (.RDS) updated under inst/testdata/create_test_data.R
• [x] 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
• [x] New/revised functions use appropriate naming conventions
• [x] New/revised functions don't repeat code
• [x] Code changes are less than 250 lines total
• [x] Issues linked to the PR using GitHub's list of keywords
• [x] The appropriate reviewer is assigned to the PR
• [x] The appropriate developers are assigned to the PR
• [x] 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]

Looks like the solution we want :+1:

Is there any way for us to force/trigger the deleted project response in a test? I think using str_detect() is fine here, but if for some reason Will/REDCapR were to change the message it feels a little fragile and it would be nice to easily identify a change like that.

https://github.com/CHOP-CGTInformatics/REDCapTidieR/blob/ba782a6d2c1cb22a1090a07742c270b28f010f85/R/utils.R#L659-L661

Can we also add these to the cli_message_examples.R file?