feat(Tabs): remove freezeContents & placeholder props

[kkafar]

Description

Remove freezeContents & placeholder props
We no longer intend to support freeze integration directly.
We push this possibility to downstream solutions, which have all
necessary building blocks to integrate with react-freeze.

Closes https://github.com/software-mansion/react-native-screens-labs/issues/979

Changes

I've removed them from public types & also removed logic inside TabsScreen component
that has been there to facilitate freeze integration.

I've also updated / removed tests that used these props. Please see particular commits for details.

Visual documentation

N/A

Test plan

We've removed a feature. We no longer need to test for it.

Checklist

• Included code example that can be used to test this change.
• Updated / created local changelog entries in relevant test files.
• For visual changes, included screenshots / GIFs / recordings documenting the change.
• For API changes, updated relevant public types.
• Ensured that CI passes

[Copilot]

Pull request overview

This PR removes the freezeContents and placeholder props from the experimental Tabs.Screen API and deletes the corresponding react-freeze integration logic from the TabsScreen component, pushing freeze behavior to downstream integrations.

Changes:

• Removed placeholder and freezeContents from TabsScreenProps public typings.
• Removed react-freeze usage and all shouldFreeze/visibility-tracking logic from TabsScreen.

Reviewed changes

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

File	Description
src/components/tabs/TabsScreen.types.ts	Removes the two public props from the TabsScreenProps interface.
src/components/tabs/TabsScreen.tsx	Removes Freeze wrapper and freeze decision logic from the component render path.

---

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

[Copilot]

There’s a commented-out bottomTabsDebugLog block that still interpolates nativeViewIsVisible, but that state was removed. This comment is now misleading and easy to accidentally uncomment into a runtime error; please delete it or update it to match the current state/props being logged.

Suggested change

	// `TabsScreen [${componentNodeHandle.current ?? -1}] render; tabKey: ${
	// rest.tabKey
	// } isFocused: ${isFocused} nativeViewIsVisible: ${nativeViewIsVisible}`,
	// );
	// `TabsScreen [${componentNodeHandle.current}] render; tabKey: ${rest.tabKey} isFocused: ${isFocused}`,
	// );

[kligarski]

We can also remove enableFreeze(true) from tests related to bottom tabs (it shouldn't be there in the first place as we have global switch in App.tsx) like Test3596, TestBottomTabs, ... but it's not necessary to proceed.

[t0maboro]

It would be great to coordinate this with other PRs introducing breaking changes to Tabs, so we can handle them with a single compatibility flag.