handling new releases of jspsych

[CrumpLab]

Currently a copy of the jspsych library is hard coded into the jspsychr template (e.g., in the inst folder).

This means users of jspsychr may not have the most recent release (assuming they always want the most recent) when they load up the template.

I'm currently looking into whether a function can be run on the users end during creation of the rmarkdown template. If this is possible, the function could populate the template with the most recent version of jspsych.

This kind of updating would have further effects on the template, which is currently written for a particular version. If the version numbering was changed (e.g., the folder might have a newer version number), then the template would need to be updated when it calls the jspsych libraries (e.g., in index.rmd).

Also worth considering writing a function to pull the most recent jspsych release.