Check that fns are pipe-compatible

[mpadge]

Idea from @PietrH via internal https://ropensci.slack.com/archives/C05C3GP1CSU/p1719994234029299, to check that

That functions that return objects of the same class as their input, have this input argument in the first position (for pipe compatability)

Or even to ensure that functions return consistent output, also as per tidyverse style guide. Implementing directly would, however, be arguably proscriptive. There may indeed be valid cases for alternative API designs, so this would need to be carefully thought out. Implementation would nevertheless be relatively straighjtforward, and would only require additional typetracer dependency here. @PietrH also happy to further discuss ideas, approaches, and viability here. Thanks for the input!

[PietrH]

Several design principles align with this general idea:

• Putting the most important argument first: https://design.tidyverse.org/important-args-first.html, the input object is probably required and the most important in the eye of the user.
• Type stability, being able to predict the output of a function based on it's input: https://design.tidyverse.org/out-type-stability.html: If I put a data.frame in a function that I expect to make a change to my data.frame, I want the output to be a data.frame.