Check if all examples run successfully

[IndrajeetPatil]

\donttest examples are run in an additional check by BDR, and probably \dontrun examples are also run in some other checks.

Therefore, making sure all examples run successfully (or are never run if they are just for illustrative purposes) is a good preventive practice in general.

This PR does that and also adds a workflow to catch such failures in the future.

[codecov-commenter]

Codecov Report

Merging #1068 (467d2f4) into main (55e8559) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1068   +/-   ##
=======================================
  Coverage   91.06%   91.06%           
=======================================
  Files          46       46           
  Lines        2685     2685           
=======================================
  Hits         2445     2445           
  Misses        240      240           

Impacted Files	Coverage Δ
R/parse.R	87.95% <ø> (ø)
R/rules-line-breaks.R	100.00% <ø> (ø)
R/set-assert-args.R	90.47% <ø> (ø)
R/transform-files.R	97.41% <ø> (ø)
R/ui-styling.R	100.00% <ø> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[lorenzwalthert]

Sure why not. Never heard of these additional checks. Is there documentation for those?

[IndrajeetPatil]

Yes, all additional checks can be found here. There is README.txt in each folder that describes the details of that check.

[github-actions]

This is how benchmark results would change (along with a 95% confidence interval in relative change) if 55e8559 is merged into main:

•   :ballot_box_with_check:cache_applying: 37.2ms -> 36.5ms [-4.14%, +0.73%]
•   :ballot_box_with_check:cache_recording: 1.17s -> 1.17s [-1.18%, +0.42%]
•   :ballot_box_with_check:without_cache: 2.94s -> 2.95s [-0.32%, +0.92%]

Further explanation regarding interpretation and methodology can be found in the documentation.