Feature!(#51): use native r pipe, replacing magrittr

[andybeet]

Your commits explain the who, what, where and when of these changes. Your code shows the how. You do not need to reiterate this. This PR should complete the big picture by telling the why.

Justification

Package heavily depended on magrittr. After updating all of the tidyverse verbs in an earlier release, whic use the native pipe, we had a mix of pipes throughout the package. Seemed like good practice to update the Rversion dependence to use the native pipe throughout

fixes #51

Types of changes

What types of changes does your code introduce? Put an x in the boxes that apply. This will inform version updates

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Other change (if none of the other choices apply)

Reviewer instructions:

devtools::check() and pkgdown::build_site() and make sure all automated tests pass

Formatting

This repo contains an air.toml file that automatically formats code to a set of standards.
It is preferred that contributors and reviewers install the air formatting tool.