openforis-collect 4.0.105

[samford]

---

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.

---

openforis-collect is autobumped but the workflow failed to update to version 4.0.105 because the dmg file wasn't available when livecheck detected the new version, as the livecheck block is set to check the GitHub repository instead. This updates the version and updates the livecheck block to use the approach that we use for other Maven packages, so the check is aligned with the asset source.

For what it's worth, I have an in-progress Maven strategy that I need to dust off and create a PR for, as we've accumulated enough packages that use this approach.