llama.cpp b3003 (new formula)

[carlocab]

• Have you followed the guidelines for contributing?
• Have you ensured that your commits follow the commit style guide?
• Have you checked that there aren't other open pull requests for the same formula update/change?
• Have you built your formula locally with HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>, where <formula> is the name of the formula you're submitting?
• Is your test running fine brew test <formula>, where <formula> is the name of the formula you're submitting?
• Does your build pass brew audit --strict <formula> (after doing HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>)? If this is a new formula, does it pass brew audit --new <formula>?

---

Closes #172186
Closes #169894

[Vaibhavs10]

This looks way more robust than my attempt! Thanks, @carlocab & @SMillerDev - I've learnt a great deal from you two in the past couple of days! 🤗

[carlocab]

macOS 12-x86_64 failure looks like a flake. I'll just dispatch a bottle separately.

[github-actions]

@carlocab has requested bottles to be published to this PR.

[github-actions]

❌ @carlocab bottle request for llama.cpp failed.

[Vaibhavs10]

Quick question, @carlocab / @SMillerDev: Should we merge PRs for the latest releases, too (via auto bump)? I see that there are new releases in llama.cpp, but I don't see any open PRs from BrewTestBot.

[carlocab]

Should hopefully be fixed by #172946.