[RFC]: add workflow to label potential duplicated PRs

[Planeshifter]

Currently, we regularly get multiple people submitting fixes for the same issues, particularly the ones for resolving commit comments. Since contributors use different names for their PRs, it's not always straightforward to identify when that happens. This RFC proposes adding a new workflow that runs on a daily schedule and does the following:

• check all open PRs on the development repository for ones that resolve the same issues, as identified via "Resolves/Closes ".
• attaches a "Potential Duplicate" label to all such identified PRs

Time estimate with AI: 60min
Time estimate without AI: 90min

Prior Task Exposure: 4
External Resource Needs: 2

[Planeshifter]

PR-URL: stdlib-js/stdlib#6081

Loom Recording: https://www.loom.com/share/06a0748d527545f1b93093a4367aa656?sid=26eda7ba-9b69-4cc0-8683-908bc2bdfda7

Time to completion: 41min.

AI Model: Claude Sonnet 3.7

Time after initial PR review: 5min.

[Planeshifter]

Notes: Very nice experience, coming to love the Cursor Agent. Compared to VSCode Copilot, where applying any changes from the chat takes ages, in Cursor it is a breeze and updates are made instantly. Code had some small bugs but model was able to resolve them quickly.

[Planeshifter]

Time after PR got merged: 32min.

https://www.loom.com/share/a1412969ea1c4180a08b20287b64061a?sid=0f6c22dd-01f0-4a2e-8c27-29c9b60268de