Update sqlcl links

[bamcgill]

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

Updating sqlcl so that we always reference the latest install so a user does not have to set an environment variable each time.

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.

---

If AI was used to generate or assist with generating the PR:

• I used AI to generate or assist with generating this PR. Please specify below how you used AI to help you.
• I have personally reviewed, tested and verified all changes/additions, including zap stanza paths.

---

[bamcgill]

This change is to set the latest downloaded version and link it to the latest reference in Caskroom/sqlcl/latest/sqlcl/bin so the user does not have to redo the environment variable for PATH each time we update.

[bevanjkay]

Hi @bamcgill

my feedback on a similar change from December remains here;

I understand that the clash with sql makes this unable to be installed automatically to due to the conflict. But looking at the other package managers that have this available the binary is almost always linked as sqlcl, I think that is going to be our best course of action here, as postflight blocks are not tested, and are therefore more likely to break.

If necessary we could add a caveat making it clear that the binary is renamed.