keeper-commander: use brewed pydantic-core

[daeho-ro]

• 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>?

---

[Copilot]

Pull Request Overview

This PR updates the keeper-commander formula to add new dependencies and upgrade existing ones. The changes involve adding macOS-specific PyObjC framework dependencies, adding a new cbor2 resource, and marking several Python packages with :no_linkage to prevent unnecessary linking.

Key changes:

• Added :no_linkage flag to certifi, cryptography, pillow, and pydantic-core dependencies
• Added four new PyObjC resources (core, cocoa, localauthentication, and security frameworks)
• Updated several Python package versions (deprecated, fpdf2, keeper-pam-webrtc-rs, wrapt)
• Added cbor2 as a new resource
• Moved pydantic-core from resources to top-level dependencies
• Modified install method to exclude PyObjC packages on Linux

[cho-m]

pyobjc* resources are often a sign we need extra_packages as autobump CI runs on Linux.

[github-actions]

🤖 An automated task has requested bottles to be published to this PR.

Caution

Please do not push to this PR branch before the bottle commits have been pushed, as this results in a state that is difficult to recover from. If you need to resolve a merge conflict, please use a merge commit. Do not force-push to this PR branch.