Stop fetching bottle manifests when creating tabs

[MikeMcQuaid]

• Formula#bottle now checks compatible_locations?, which fetches the bottle manifest when the tab metadata is not yet cached.
• Tab.create runs inside the build sandbox and called this for every runtime dependency, so formulae with a fetch phase failed to install once the sandbox denied the cache write.
• The dependency's rebuild number only depends on the bottle spec for the current tag, so read it without the location check.

Fixes #23759

---

• Have you followed our Contributing guidelines?
• Have you checked for other open Pull Requests for the same change?
• Have you explained what your changes do? Performance claims (e.g. "this is faster") must include brew benchmark results.
• Have you explained why you'd like these changes included, not just what they do?
• For bug fixes, have you given step-by-step brew commands to reproduce the bug?
• Have you written new tests (excluding integration tests)? Here's an example.
• Have you successfully run brew lgtm (style, typechecking and tests) locally?

---

• I did not use AI/LLM to create this PR, or I disclosed the tool/model below and reviewed its output; I did not attribute commits to AI and will answer maintainer questions and review comments myself without AI/LLM.

Claude with Fable at High effort, with local review and testing.

---

[Copilot]

🟢 Approval recommended

The focused change fixes the sandbox failure while preserving tag-specific rebuild metadata and includes appropriate regression coverage.

Pull request overview

Prevents bottle manifest fetches while recording dependency metadata in installation tabs.

Changes:

• Reads rebuild numbers directly from the bottle matching the current platform tag.
• Adds regression coverage ensuring location compatibility is not checked.

File summaries

File	Description
Library/Homebrew/tab.rb	Avoids compatibility checks when recording bottle rebuilds.
Library/Homebrew/test/tab_spec.rb	Tests rebuild recording without location checks.

Review details

• Files reviewed: 2/2 changed files
• Comments generated: 0
• Review effort level: Balanced

---

💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.