Add utils/backtrace requires

[samford]

• Have you followed the guidelines in our Contributing document?
• Have you checked to ensure there aren't other open Pull Requests for the same change?
• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your changes? Here's an example.
• Have you successfully run brew style with your changes locally?
• Have you successfully run brew typecheck with your changes locally?
• Have you successfully run brew tests with your changes locally?

---

This is primarily intended to resolve the uninitialized constant Utils::Backtrace error in formula_versions.rb:60 (e.g., https://github.com/Homebrew/homebrew-core/actions/runs/9942660636/job/27464770982?pr=177398, from Homebrew/homebrew-core#177398) but I expanded it to try to cover all existing usage of Utils::Backtrace.

Per Rylan's comment below, I've followed the existing pattern, where utils/backtrace is required in the context of where it's used. Many of these cases use Backtrace in a conditional manner, so I've tried to ensure that the require follows suit.

[Rylan12]

I'm not opposed to this, but it does feel like this shouldn't go in formula.rb if there is no direct call within this file.

It looks like it's used in 12 files (not including tests and other sorbet stuff). Maybe it's better to add it to those directly instead? I'm not sure how much of a performance difference it makes.

For context, I did this last time (not claiming this is the best way though): https://github.com/Homebrew/brew/pull/17738/files

[samford]

I updated this to cover all the instances that I found where Utils::Backtrace is used but there's no require "utils/backtrace". If it's already available in any of these contexts, just let me know and I can pare this back accordingly.

I generally used the approach that @Rylan12 linked to, where utils/backtrace is required in the context of where it's used (instead of at the top of the file). When there were conditions around the use of Utils::Backtrace, I tried to have the require respect the same conditions (with the exception of odebug calls requiring a debug context).

One thing to note is that cask/audit.rb requires utils/backtrace at the top of the file. If you remove that and only require it where Utils::Backtrace is used, it leads to errors when running brew tests. There may be a way to resolve that issue but I figured it would be best to leave it alone for now.

I would appreciate more eyes on this, as I'm not sure if this is the best way to go about it all.

[Rylan12]

Looks great, thanks @samford!