Fix two wrong issue references

[def-]

Follow-up to #29773

Checklist

• This PR has adequate test coverage / QA involvement has been duly considered. (trigger-ci for additional test/nightly runs)
• This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
• If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
• If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).
• If this PR includes major user-facing behavior changes, I have pinged the relevant PM to schedule a changelog post.

[def-]

I just figured out why they went wrong, the replacements could catch part of an issue reference, for example materialize#12345 would get a replacement materialize#1234 -> database-issues#999, resulting in database-issues#9995, which is a totally invalid number. Will rerun my script with that fixed and see if anything else turns up.