Support using a repo slug that doesn't match package name #12
Description
Right now, we assume the package name on CRAN (that appears in the description) will be the same as the Github repository name that is used as the slug in Github links.
We don't currently observe this constraint in the econdataverse packages, where the package name might be "wbids", but the slug might be "r-wbids".
To support the econdataverse naming convention, we should modify the template to use two different placeholders.