[General] Don't activate buttons on start

[j-piasecki]

Description

Changes shouldActivateOnStart on buttons to false - true breaks nested buttons on Android.

cc @m-bert - I don't recall why it was true in the first place, any chance that after #4116 it wouldn't have been needed anyway?

Test plan

Before	Update
Screen.Recording.2026-04-24.at.14.34.36.mov	Screen.Recording.2026-04-24.at.14.34.17.mov

[Copilot]

Pull request overview

This PR adjusts the default activation behavior for v3 “button” wrappers to avoid Android issues with nested buttons by no longer activating the underlying NativeViewGestureHandler immediately on touch start.

Changes:

• Set shouldActivateOnStart to false for v3/components RawButton (and, transitively, BaseButton/RectButton/BorderlessButton built on it).

---

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

[m-bert]

cc @m-bert - I don't recall why it was true in the first place

This was changed in #4036 in order to get rid of strange platform dependent workarounds in buttons.

any chance that after #4116 it wouldn't have been needed anyway?

Probably. I think in that case we should also check if we should swap onBegin with onActivate in buttons (as you did in Touchable).

[j-piasecki]

I think in that case we should also check if we should swap onBegin with onActivate in buttons (as you did in Touchable).

Do we want to do that in the buttons given, which are deprecated (and this will likely result in a behavior change)?

[m-bert]

Do we want to do that in the buttons given, which are deprecated (and this will likely result in a behavior change)?

If they work correctly after this, then we don't have to change it. I've looked at examples and they seem work (at least in case of callbacks) so I guess we can ship it