Link for bugs.chromium.org expires

Links expire after using a new issue track website, for example, the following link is in the readme.md:

https://bugs.chromium.org/p/oss-fuzz/issues/list?q=Type%3DBug-Security%20label%3Aclusterfuzz%20-status%3ADuplicate%2CWontFix&can=1

But it redirects people to the new issue tracker which can't tell the correct number of vulnerabilities that OSS-Fuzz found.

A further request: Is it possible to link the new ID (new issue tracker) to the old ID?

For example: the old ID is 38900, when we visit `crbug.com/oss-fuzz/38900` the site redirects us to `https://issues.oss-fuzz.com/issues/42502089` but we can't find any information about 38900 in the new page. It's also great if you can tell the rules to map old ID to the new ID.

Start with the readme.md link to the bugs.chromium.org query and verify how it redirects in the current issue tracker. Determine whether the old and new vulnerability IDs can be mapped or documented from the available tracker information. Done means the README link works or is replaced, and any confirmed ID-mapping guidance is recorded.

Written by the indexing model from the issue text.