Fix non-chr/numeric casting in apply_labs_haven()

[ezraporter]

Description

This PR fixes test failures occurring against the development version of labelled().

My initial implementation of apply_labs_haven() was more general than it needed to be and introduced a test failure on a radio button variable where both the data values and labels are missing and therefore NA_logical. haven::labelled() explicitly accepts only character and numeric data types so we don't actually have to account for data values of other data types and can just cast to character when they occur.

I also removed a failing test for a specific error message when the API returns status code 405. We were hitting google to generate the status code and it now returns 404. Not sure it's worth testing these.

Proposed Changes

• Remove failing status 405 test case
• Update force_cast() and apply_labs_haven() to fall back to converting to character when non-numeric data types are encountered

Issue Addressed

closes #189

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/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/1207023454671921

[rsh52]

Two small comments, otherwise looks good. 👍