No PNG images with new TeXLive: Use version-stable TinyTeX about smarp

[riccardoporreca]

Usage of version-stable TinyTeX implemented with 0a69df4 in a feature branch, where we use as date 2019/02/27, which is the latest snapshot available before the MRAN build date of the rocker/r-ver:3.5.3 we are currently using and corresponds to the frozen 2018 TeXLive snapshot.

Successfully tested in the feature branch via

git checkout feature/152-version-stable-tinytex
docker build --pull -f Dockerfile -t mirai/smarp:152-version-stable-tinytex .
docker run -p 80:80 mirai/smarp:152-version-stable-tinytex

[riccardoporreca]

Note that, in general, we shall reconsider if we want to keep using xelatex as engine, as well as whether PDF version (vector graphics) of the figures can be created and used instead of PNG.

This can be addressed as part of #130.

[riccardoporreca]

After some more thoughts, one option to pick the TeXLive snapshot is to bind it to the version of TeXLive normally shipped as texlive-* packages in the Debian image each rocker/r-ver is created FROM. This would basically mean using the TinyTeX install in the rocker/verse as a tiny, container-friendly replacement for the TeXLive install one would get via apt-get for the specific Debian release.
The information can be found at https://www.tug.org/texlive/debian.html.

Originally posted by @riccardoporreca in rocker-org/rocker-versioned#169 (comment)

It then makes sense to use the TeXLive 2016 release from the tlnet archive, i.e. http://www.texlive.info/tlnet-archive/2017/04/13/tlnet as CTAN_REPO. Note the http instead of https, this is required since back in TeXLive 2016 install-tl only supported http and ftp for the -repository command-line argument.

This is even more relevant for SmaRP, where we are doing a first release where we switch from the debian texlive-* packages to TinyTeX, and this approach would minimize the difference in the PDF report due to the version of TeXLive and LaTeX packages.