ultdata: update livecheck, use versioned url

[khipp]

Important: Do not tick a checkbox if you haven’t performed its action. Honesty is indispensable for a smooth review process.

In the following questions <cask> is the token of the cask you're submitting.

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.

---

Related to #171006.

[samford]

Looking in the app, it appears that 1053 is the product ID (there are strings like "ProductURL" = "http://cbs.tenorshare.com/go?pid=1053&a=dp"), so this approach may not be any more versioned than the existing URL.

If 1053 was a number that would change (e.g., a build number, etc.), I'm still not sure where we stand on using a version that doesn't include the app version. Usually we would use something like 9.7.27,1053 (or 9.7.27.12,1053) and version.csv.second in the url but that's not feasible since we can only identify the version using ExtractPlist.

It would be good for someone else to check my work but that's what I'm seeing from a quick look.

[krehel]

Agreed with @samford. Read this yesterday, forgot to comment. I'm not in favor of this, sorry.

[khipp]

Agreed, I will close this one then. Thanks anyway!

[krehel]

No worries @khipp - it happens! Thanks for the contribution. ❤️