Review error messages

[olivroy]

Summary

• use standalone types check
• Use error chaining
• Use tidyverse style for errors.

For review, I'd suggest to look at code here, but if you want to have a visual feel of how this translates in real-life, I added links to important commits in #1681 that may help pinpoint the essence of the PR.

To have an idea of how this PR improves things.

Look at 472510f in #1681 which displays how certain messages improved.

30938f0 also helps to see the visual impact of some of my previous changes.

See #1681

Related GitHub Issues and PRs

Fixes #1681.
Related to #1638 and #1640.

I may add snapshot tests eventually, but given the size of the PR, I don't want to commit too many changes that may slow down development. (It took me a while to get all checks passing because of the size of the PR)

Checklist

• I understand and agree to the Code of Conduct.
• I have listed any major changes in the NEWS.
• I have added testthat unit tests to tests/testthat for any new functionality.

[rich-iannone]

LGTM, thank you for this!

[rich-iannone]

Let me know if you plan any more changes for this (just want to be sure of it).

[olivroy]

I was done with my changes here, unless changes are requested.