fix: Safely parse announcement Flag

[kyle-ssg]

Thanks for submitting a PR! Please check the boxes below:

• I have run pre-commit to check linting
• I have filled in the "Changes" section below?
• I have filled in the "How did you test this code" section below?
• I have used a Conventional Commit title for this Pull Request

Changes

Instead of trying to JSON parse a feature flag without catching, the frontend will now safely handle the non-json type by providing a fallback.

Please describe.

How did you test this code?

Tried with / without a null, json and undefined announcement as well as dismissing the announcement.

Please describe.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 28, 2023 9:15am
flagsmith-frontend-preview	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 28, 2023 9:15am
flagsmith-frontend-staging	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 28, 2023 9:15am

[github-actions]

Uffizzi Preview deployment-41603 was deleted.

[sentry-io]

Suspect Issues

This pull request was deployed and Sentry observed the following issues:

• ‼️ TypeError: null is not an object (evaluating 'window.localStorage.setItem') _class.render(web/components/App) View Issue
• ‼️ TypeError: null is not an object (evaluating 'window.localStorage.setItem') _class.render(web/components/App) View Issue

_{Did you find this useful? React with a 👍 or 👎}