Move materialize issue references to database-issues

[def-]

Collected the issues via

git grep "https://github.com/MaterializeInc/materialize/issues/" | sed -e "s/.*issues\/\([0-9]*\).*/\1/g" | sort -n | uniq
git grep "materialize#" | sed -e "s/.*materialize#\([0-9]*\).*/\1/g" | sort -n | uniq > out

Then found the correct new urls via

while read line; do curl --header "Authorization: Bearer $GITHUB_TOKEN" --header "X-GitHub-Api-Version: 2022-11-28" "https://api.github.com/repos/MaterializeInc/materialize/issues/$line" -s | jq -r ".url" ; done

And ran sed commands to replace them. I'm not sure if we actually want this, but I prefer to have the actual link instead of one that will be redirected.

Follow-up to #29716

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.

[benesch]

Thanks! I prefer this as well.

[chaas]

Thanks @def- ! Good idea