Fixes #471 , adding support for the \textsc command via the small caps font cmcsc10. Thanks to everyone who suggested solutions in the original thread. I'm willing to take this over the finish line, but will need a bit of assistance verifying that the changes I made are reasonable.

For future reference, these are the steps I needed to take (inside the dev container) to run the font generation scripts on my machine:

• sudo apt install mftrace fontforge fonttools ttfautohint texlive-fonts-recommended (should these be added to the dev container?)
• modify src/fonts/Makefile to call perl with perl -I . since @INC no longer includes the current working directory in recent Perl versions
• sudo apt-get install python-pip
• pip install fonttools zopfli brotli
• ./dockers/fonts/buildMetrics.sh
• cd src/fonts && make clean && make all

Output for \textsc{Lorem Ipsum Dolor}

Questions / Concerns:

1. I'm not sure how to deal with combinations of font weight/shape/style (esp in src/buildCommon.js). Not all combinations are valid, and I'm not sure what the desired priority is, so I made my best guess.
2. Should anything be added to src/fonts/makeFF or src/fonts/makeBolder?
3. In the Chrome inspector, unchecking the "font-style" property of any text command (like \textit, \textsc, \mathbf, etc.) causes the text to render as small caps. Why might this be? How to fix it?
4. What's the difference between src/fonts/makeFF and src/metrics/mapping.pl? Is one generated from the other? Should they be kept in sync somehow? The changes I made to each were just my best guess.
5. How should the documentation be updated? I see some font prefetching instructions at docs/browser.md which I suspect will need to be updated with the new font.
6. All existing tests (jest and screenshots) pass on my machine. What kind of tests should be added for the new font and command?