Fix map controls and resolve Analyses Message issue

[dzole0311]

Related Ticket: #1155 #1172

Related Next.js PR: NASA-IMPACT/next-veda-ui#7

Description of Changes

• Fixed the map controls so that they work in the Next.js instance
• Resolve issue with the Analyses Message display
• Attempted to address the React mount error mentioned in Clean up the themed controls when unmounted #1172

Notes & Questions About Changes

{Add additonal notes and outstanding questions here related to changes in this pull request}

Validation / Testing

1. Verify that the AOI controls and Analyses Message work as expected in both veda-ui and the Next.js instance
2. Verify that adding, deleting a single drawn area, or deleting all drawn areas works without issues
3. Ensure that analyses execute as expected

[netlify]

✅ Deploy Preview for veda-ui ready!

Name	Link
🔨 Latest commit	c6aadaf
🔍 Latest deploy log	https://app.netlify.com/sites/veda-ui/deploys/6720a21298d23d00085aa26a
😎 Deploy Preview	https://deploy-preview-1205--veda-ui.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[sandrahoang686]

@dzole0311 have you tried running this locally with the nextJs instance feature branch code? I've run them both with npm link and kept running into this error? Do you encounter the same?

[dzole0311]

@sandrahoang686 I attempted to fix that issue, but it still occurs. It's unrelated to this PR and we can fix it in a follow-up.

[sandrahoang686]

@dzole0311 unsure how to test then? could we re-comment out what was causing that error again and add an @TODO to fix that because this would block E&A then. Looking at the original PR hanbyul opened, doesn't look like we have a ticket for it either. We would need to create that as part of a follow-up and have it as part of shipping/exposing E&A

[sandrahoang686]

@dzole0311 unsure how to test then? could we re-comment out what was causing that error again and add an @TODO to fix that because this would block E&A then. Looking at the original PR hanbyul opened, doesn't look like we have a ticket for it either. We would need to create that as part of a follow-up and have it as part of shipping/exposing E&A

[sandrahoang686]

@dzole0311 this works in safari for me but in chrome I keep seeing that error even after hard refreshing and going in-cognito so must be something on my end but it looks to be working 👍🏼

[dzole0311]

@sandrahoang686 Thanks again for testing. I removed my fix attempt as it did not fix the issue, and opened a new ticket with details since it occurs in the stories as well as the E&A page: #1221

[hanbyul-here]

aha I think I am seeing the problem you saw @sandrahoang686 . Each component works separately (ex. only modal was used , only EA was used) but when they are put together, they don't seem to stably work together. (Also it works sometimes, and doesn't sometimes. I can't reproduce the error stably 🤔 ) I am looking at the issue 🔍