Increase Bridge serialization threshold from 1 -> 2

[bvaughn]

This basically reverts #1258. It is being done to fix interaction names within the Profiler.

Resolves #1262

[gaearon]

Can we fix just the profiler stuff alone somehow?

[bvaughn]

Can we fix just the profiler stuff alone somehow?

Requests sent through the Bridge are batched and treated pretty generically.

Maybe the profiler could proactively "hydrate" interactions during the commit phase (the only time when we know the data will actually still be around to hydrate) so that we serialize a little more information about them? This would slow down the commit phase though.

I can give it a little more thought before merging this I guess.

[bvaughn]

After thinking about this a little more, I don't think there's a great alternative (that would not involve making more significant changes to the bridge architecture).

I considered trying to explicitly hydrate the root fiber's memoizedInteractions set during the commit phase (when profiling), but I think this wouldn't work– since the ProfilerStore assumes things can be committed synchronously but bridge hydration is asynchronous.

I also briefly considered trying to special case the serialization threshold for root fibers and/or the interactions Set somehow but I'm not sure how that could be cleanly accomplished with the current layers of abstraction.