[NO QA] Improve documentation around React StrictMode

[Kicu]

Coming from this long discussion in slack: https://swmansion.slack.com/archives/C05LX9D6E07/p1724834166631849?thread_ts=1722970682.900369&cid=C05LX9D6E07

It seems that our usage of StrictMode is still confusing to developers and we do not have a lot of comments or docs written about this.
I will update some of our readmes to write most important points and drop some links for further reading.

This will be only a doc update, no code logic changes intended.

Action Performed:

N/A

Expected Result:

N/A

Actual Result:

N/A

Workaround:

N/A

[melvin-bot]

Triggered auto assignment to @stephanieelliott (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[melvin-bot]

📣 @chenshupe! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:

1. Make sure you've read and understood the contributing guidelines.
2. Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
3. Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
4. Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
   
   Format:

Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>

[Kicu]

@chenshupe bad bot

[Kicu]

I believe this issue can be closed. This was only a docs change, no changes to app, no QA or testing required, and no C+ was involved with reviewing.

If I forgot about something then please comment and/or reopen.
CC @mountiny