Update citation_count.json independently and on a schedule

[ethanwhite]

Having citation_count.json get automatically updated and included in other changes can be confusing and clutter the history (e.g., see #1011). Let's shift to having a separate GitHub Action that runs once a week and updates that file automatically to keep those updates separate from the general contribution workflow.

Does that sound reasonable to you @henrykironde?

[naxatra2]

I’ve noticed that using --no-verify with the git commit command can help bypass the citation_count.json issue. However, this approach can be problematic especially for someone new to the repository since it skips style checks that may later fail during CI testing.

[ethanwhite]

Thanks @naxatra2. I agree both that this approach works and that it's not the best solution in the long run. We really just want to separate that code out and have it running regularly on CI

[bw4sz]

Assigning @henrykironde since this is the kind of thing we might want to do on multiple repos and good to have the knowledge within the lab.