Dev vs. Prod workflow

[JohnCoene]

This would definitely require dev and prod builds but I feel it could be handled better.
Having to switch manually I know I'm personally bound to make mistakes myself.

This issue may be somewhat relevant.
I raised this issue for packer which is similar to this project but
for JavaScript in a sense.

If we have dev and prod I think we need a way to ensure users do not publish to CRAN or push to github
dev code. My idea with the issue above was not with document but with devtools::check.

Current alternative in packer Github pre-commit hook to check that output files are bundled, similar
can be done here but still does not protect from pushing dev to CRAN.

[krlmlr]

We can make the dev mode add something that would fail R CMD check but otherwise not affect the functionality of the code.

I double-checked clean and smudge filters, they might work for inline preprocessing but we wanted to move away from that in the longer run.

[moodymudskipper]

We might have a Q folder inside of the R folder, the structure is legal and files in the Q folder are ignored when building the package.

The R files would be locked so user doesn't mess up with them, rpp_to_dev() (or a newly named function) would synchronise the R files with the Q files (which might have extension .q).

rpp::load_all() would load the "Q" folder rather than the "R" folder

This also ensures the tests are always run with the dev code.