perf(Announce): Batch getComputedStyle reads to avoid layout thrashing

[mattcosta7]

Closing - No meaningful performance impact

This PR was originally created as part of the INP optimization effort (#7312), but upon review, the change has no measurable performance impact.

What the change does

// Before
const style = window.getComputedStyle(element)
if (style.display === 'none') {
  return
}
if (style.visibility === 'hidden') {
  return
}

// After  
const {display, visibility} = window.getComputedStyle(element)
if (display === 'none' || visibility === 'hidden') {
  return
}

Why it doesn't matter

Both versions call getComputedStyle exactly once. The original code was NOT calling it twice - it stored the result in a variable and read properties from it.

The only differences are:

• Destructuring syntax (style preference, not performance)
• One combined if instead of two (micro-optimization with no measurable impact)

Conclusion

This is a code style change, not a performance optimization. Closing to keep the PR set focused on changes with actual INP impact.

[changeset-bot]

🦋 Changeset detected

Latest commit: 9bc4202

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@primer/react	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

👋 Hi, this pull request contains changes to the source code that github/github-ui depends on. If you are GitHub staff, test these changes with github/github-ui using the integration workflow. Or, apply the integration-tests: skipped manually label to skip these checks.

[mattcosta7]

Closing - this change has no meaningful performance impact. See updated PR description for details.