Release Counter Processor under gdcc, switch docs from CDLUC3

[pdurbin]

As discussed in standup this morning in the context of this issue...

• Operationalize MDC: Create Cron Jobs, Acquire, Configure Prod Web Token, Handle Logs  dataverse.harvard.edu#3

... we decided to fork https://github.com/CDLUC3/counter-processor to https://github.com/gdcc/counter-processor because the former had been switched to archive/read-only mode (which isn't great optics).

Next we need to put out a release of Counter Processor under the gdcc repo (our current docs are written to expect a release such as https://github.com/CDLUC3/counter-processor/archive/v0.1.04.tar.gz ).

Then we need to update the guides, basically a find and replace of CDLUC3 to gdcc. Something along these lines:

By the way, I noticed that we already had https://github.com/IQSS/counter-processor but I was only using it to make pull requests into the upstream CDLUC3 repo. I updated the README to point to the new gdcc repo.

[poikilotherm]

Have you seen the reasons why they archived it? Are any of those true for us as well? Should we still use it?

On a related note: we could push the package to PyPI or GH packages for installation via pip. Would that help?

If we continue using it, I would also appreciate a container image to speed up usage and to freeze the dependencies.

[pdurbin]

In gdcc/counter-processor@4c662cd I reverted the reasons stated in the README. In short, the code was used by Dryad but not anymore now that they plan to use https://github.com/datacite/datacite-tracker instead. (We have concerns about datacite-tracker only tracking browser requests, not API calls.)