fix: remove isLaidOut check from copyBoundsInWindow method

[kirillzyusko]

📜 Description

Removed isLaidOut check from copyBoundsInWindow method.

💡 Motivation and Context

When we are using native-stack then on initial mount the view property isLaidOut will be true. When we open a new screen and return back to the previous isLaidOut will be false.

I've tried to call invalidate/requestLayout/forceLayout methods in onAttachedToWindow method, but it doesn't seem to have any effect at all.

Then I decided to compare how copyBoundsInWindow works if isLaidOut check is removed. And turned out there is no difference between two executions:

Screen opened first time (isLaidOut check present)	Returned to the screen (isLaidOut is missing to go to if-statement)

So taking this information into consideration I've decided to remove that check.

Also for the sake of safety and avoidance of unexpected crashes I decided to remove throw Exception construction and replace it with a simple logger (since I'm not handling exceptions in my code it's better to log it).

Closes #274 #203

📢 Changelog

Android

• removed isLaidOut check from copyBoundsInWindow method;
• replaced throwing error to logger.

🤔 How Has This Been Tested?

Tested on Pixel 7 Pro (android 14).

📸 Screenshots (if appropriate):

telegram-cloud-document-2-5381959313151507275.mp4

📝 Checklist

• CI successfully passed

[github-actions]

📊 Package size report

Current size	Target Size	Difference
79940 bytes	79970 bytes	-30 bytes 📉