[stable29] chore: Fix psalm CI on stable29

[DerDreschner]

• Related to: [stable29] chore: Improve SVG handling in link previews #59840
• Related to: [stable30] chore: Fix psalm CI on stable30 #61321

Summary

Since #59840, the static code analysis from psalm is broken in our CI. To make the CI pipeline green again, I've added the correct @since attribute to the function.

Checklist

• Code is properly formatted
• Sign-off message is added to all commits
• Tests (unit, integration, api and/or acceptance) are included
• Screenshots before/after for front-end changes
• Documentation (manuals or wiki) has been updated or is not required
• Backports requested where applicable (ex: critical bugfixes)
• Labels added where applicable (ex: bug/enhancement, 3. to review, feature component)
• Milestone added for target branch/version (ex: 32.x for stable32)

AI (if applicable)

• The content of this PR was partly or fully generated using AI

[DerDreschner]

Failing CI runs are unrelated. The one I try to fix with this PR were successful: https://github.com/nextcloud/server/actions/runs/29912665003/job/88899051078?pr=62400

[DerDreschner]

@SebastianKrupinski The issues with the other failing tests on stable29 are fixed in #62406. The commit from copilot has nothing to do with what's being fixed here and should be removed to keep the PR clean.

[SebastianKrupinski]

@SebastianKrupinski The issues with the other failing tests on stable29 are fixed in #62406. The commit from copilot has nothing to do with what's being fixed here and should be removed to keep the PR clean.

They I must have clicked the copilot button by mistake and didn't realize it. I was just restarting the jobs for you.

[DerDreschner]

They I must have clicked the copilot button by mistake and didn't realize it. I was just restarting the jobs for you.

All good, I've dropped the commit from copilot. Just wanted to let you know and see if that was on purpose or not. 😄