Implement publishing a release to the pdfjs-dist GitHub repository

[timvandermeij]

In #18350 the release publishing logic got ported from the bots to GitHub Actions, but the long-broken GitHub repository push logic to the pdfjs-dist repository was left out. This issue tracks reimplementing pushing to the pdfjs-dist Git repository as part of the new publish_release.yml workflow.

[timvandermeij]

Before doing this I would like to gauge if there is actually interest for this. The last push to https://github.com/mozilla/pdfjs-dist was from January 1st, 2023 and we haven't really had many questions about it, so I'm therefore not sure if just pushing to NPM alone isn't enough? Most other NPM packages also just push artifacts to NPM without also having a separate Git repository, so I'd like to collect the use cases for such a repository first.

[Snuffleupagus]

Before doing this I would like to gauge if there is actually interest for this.

I'd support deprecating the pdfjs-dist repository, simply because it'd reduce the number of things that we have to support.[1]

---

[1] If we go down this route then I'd probably suggest that we update, according to my comments, and land mozilla/pdfjs-dist#22 and afterwards we can mark the repository as "archived".

[Snuffleupagus]

I've just updated and squash-merged mozilla/pdfjs-dist#22, since that seems like the right thing to do in the short term.

---

Most other NPM packages also just push artifacts to NPM without also having a separate Git repository, so I'd like to collect the use cases for such a repository first.

From my perspective, I do think that we should add a few "restrictions" here:

• It should be technically impossible to achieve the desired outcome without the Git repository, rather than only "I prefer to not use NPM".
• There should be a number of different users and use-cases affected, since maintaining this for e.g. a single user doesn't seem feasible.

[Snuffleupagus]

I think that we should just move forward with "archiving" the pdfjs-dist repository (and perhaps also clean-up the gulpfile).

[Snuffleupagus]

Additionally, I believe from looking at old issues that a significant reason for creating the pdfjs-dist repository was to support Bower since otherwise there wouldn't have been builds to "point to" in the Bower registry.
However, note that we stopped supporting Bower almost two years ago, see PR #15390, since already by that point it'd been deprecated for a number of years.

[timvandermeij]

@calixteman Could you archive the https://github.com/mozilla/pdfjs-dist repository? There should be a red "Archive this repository" button at the bottom of https://github.com/mozilla/pdfjs-dist/settings.

[calixteman]

@calixteman Could you archive the https://github.com/mozilla/pdfjs-dist repository? There should be a red "Archive this repository" button at the bottom of https://github.com/mozilla/pdfjs-dist/settings.

Done