Fire event explorer without branded components

[aboydnw]

Context

One idea for the evolution of tools is that any branded component should be separate from the tool build. Things like the header, footer, and info modals with additional context could be separate and coming from the instance code. This would make the tools more flexible and easily adaptable.

Acceptance Criteria

• The header, footer, and info modal is separated from the Fire Event Explorer code, making it easier to change branding such as color scheme, fonts, logos.

Definition of Done

• Unit tests
• (Where applicable) Automated playwright tests to cover primary use case(s)
• Merged to develop in relevant repo
• (?) Tested in instance context (GHG, earth.gov, template instance, etc)
• Relevant details of work are shared in a team forum (PR, ticket, slack, etc) to support knowledge sharing