RG-2774 Fix ButtonGroup disabled detection with nested children

[Hypnosphi]

Summary

• Fix styles.disabled condition in ButtonGroup to recursively traverse nested children (e.g. buttons wrapped in <Tooltip>) when determining whether all buttons are disabled
• Extract isChildDisabled helper that checks disabled prop on direct button elements and recurses into wrapper elements' children
• Update story to wrap disabled buttons in <Tooltip> to demonstrate the fix

Fixes https://youtrack.jetbrains.com/issue/RG-2774

Test plan

• Verify the "all disabled" story section renders with disabled border styling
• Verify non-disabled groups are unaffected
• Verify empty ButtonGroup does not incorrectly get disabled styling

🤖 Generated with Claude Code

[Copilot]

Pull request overview

Fixes ButtonGroup “all disabled” styling when buttons are wrapped in nested components (e.g., <Tooltip>), by making the disabled detection traverse into nested children.

Changes:

• Add a recursive isChildDisabled helper and use it to compute styles.disabled for ButtonGroup.
• Update the Storybook story to wrap disabled buttons in <Tooltip> to demonstrate the nested-children case.
• Update lockfile metadata (yauzl range for @ring-ui/screenshots) and remove an .idea VCS settings block.

Reviewed changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated 2 comments.

File	Description
src/button-group/button-group.tsx	Implements recursive disabled detection to decide when to apply group disabled styling.
src/button-group/button-group.stories.tsx	Adjusts the story to include wrapped disabled buttons (Tooltip) to validate the fix visually.
package-lock.json	Updates the recorded semver range for yauzl in @ring-ui/screenshots metadata.
.idea/vcs.xml	Removes IDE GitHub shared project settings (branch protection patterns).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[aleksei-berezkin]

Because this.props.children is already ReactNode — exactly what isChildDisabled() needs — it can be passed there as is, without the conversion to an array

[Hypnosphi]

This will short circuit on !('props' in child) if there's more than one child. So I will add proper handling for that case