qidistudio: update checksum

[cub-uanic]

Updated SHA256 checksum for version 2.05.01.52, according to upstream release page https://github.com/QIDITECH/QIDIStudio/releases

---

After making any changes to a cask, existing or new, verify:

• The submission is for a stable version or documented exception.
• brew audit --cask --online <cask> is error-free.
• brew style --fix <cask> reports no offenses.

Additionally, if adding a new cask:

• Named the cask according to the token reference.
• Checked the cask was not already refused (add your cask's name to the end of the search field).
• brew audit --cask --new <cask> worked successfully.
• HOMEBREW_NO_INSTALL_FROM_API=1 brew install --cask <cask> worked successfully.
• brew uninstall --cask <cask> worked successfully.

---

• AI was used to generate or assist with generating this PR. Please specify below how you used AI to help you, and what steps you have taken to manually verify the changes, including zap stanza paths.

---

[SMillerDev]

The current checksum was generated from the downloaded file. Did upstream re-tag the release?
Because the git manual says re-tagging is "the insane thing" to do.

[bevanjkay]

It is almost impossible for @BrewTestBot to generate an incorrect checksum, because it has to be detected incorrectly across two separate, and completely isolated CI runs. In this case the developer re-uploaded the release artifacts without changing the version. These are the exact instances that checksum checks exist, to detect these changes, and check if they are nefarious.