fix: catch init error in useFlagsmith

[Zaimwa9]

Closes #347
Problem
When initial fetching of flags failed using one of the lib react hook (500, 403), the promise rejection is unhandled, causing console errors and surfacing the error to the parent app.

Changes

• Added .catch in react.tsx when calling init to prevent unhandled rejections
• emit an event to update react hooks
• Ensure flags default or disabled if not provided
• Error captured in loadingState.error

Test

• Added a test covering the case

Before fix:

After fix:

[talissoncosta]

Looks good overall. Let's just check the ; usage.

[Zaimwa9]

@talissoncosta, removed trailing comma and semi-colon from linter configuration. The diff is only coming from the linter in the new commit.
I believe the rules were set but the formatting hadn't been applied before. Let me know if you prefer different rules, i'm not strongly opiniated

[talissoncosta]

@Zaimwa9 thanks for handling that. It looks pretty good to me.
Yep, I see what you mean, It is all good to me, as long as we apply the same rules we don't add extra changes to the PRs.