[Performance] Move SearchRowSkeleton to top level SearchPage

[luacmartins]

Problem
When users navigate to the Reports page, if they don't have local data we show the loading skeleton rendered by the Search component. The Search component has heavy subscriptions and logic unnecessary to display the loading skeleton, which delays the user interaction.

Solution
Move SearchRowSkeleton to the top level SearchPage component.

Issue Owner

Current Issue Owner: @szymonzalarski98

[szymonzalarski98]

Have an initial solution for this, but need some time for measurements

[luacmartins]

@szymonzalarski98 how's this one going?

[szymonzalarski98]

@luacmartins Plan for today is to create an internal proposal and draft PR

[szymonzalarski98]

Hey, @luacmartins I'm really sorry, but I found an issue in my implementation and have a delay, today I'm going to create a proposal and a draft PR

[luacmartins]

No worries. Thanks for the update!

[szymonzalarski98]

@luacmartins Created a draft PR and posted an internal proposal for Callstack team.

[szymonzalarski98]

Hey, today I was fixing comments but the PR is not ready to be updated because I'm noticing a bug with loading

[szymonzalarski98]

Hey, still struggling with a regression, the issue must wait a bit for new commit

[szymonzalarski98]

Hey, PR is updated, ready for review

[szymonzalarski98]

PR is still in review, but there is a problem with Prettier and I don't have clear understanding why the error happens, trying to solve it

[szymonzalarski98]

I see there are some comments from reviewer, fixing it right now