Should not include development scripts in the inst dir

[eitsupi]

There are many files not related to users now.
We should move these files out of the inst folder.

[eitsupi]

@sorhawell I think these files are actually only used by you, so can I ask you to update them?

[sorhawell]

I will move them to dev.

@eitsupi are you brewing on some new task format?

Maybe it is a pity these dev functions are not being promoted more. @etiennebacher had issues with rust and make "cache" (rust target dir + previous built binaries) did not work across branches etc. I think it is possible to use the Makefile but the environment variables have to be set just right, and sometimes by accident the previous compilation is lost. It is likely so because the Makefile first serves our CI and contains GOTCHAS because of CRAN rules and cross compilation etc.

With load_polars / build_polars / check_polars it just a one liner from the R terminal and I never lost an opportunity to reuse the target files/ previous built binaries again ... and then the 2 secs! for spawning a new R process saved also :)

I could add to Makefile opinionated load / install / check procedures focused on speed.

[eitsupi]

are you brewing on some new task format?

It's on my TODO list but I've been so busy lately I haven't had time to do it.

[eitsupi]

@sorhawell I opened a PR #617
Tasks can have environment variables set per taskfile or per individual task, so there is no need to worry about environment variables in R.

r-polars/Taskfile.yml

Lines 3 to 6 in c1c72d6

	env:
	NOT_CRAN: "true"
	LIBR_POLARS_BUILD: "true"
	RPOLARS_FULL_FEATURES: "true"