feat(dashboards): enable optional light mode for dashboards

[alexpaxton]

• Create key in redux state to determine how to render dashboards
• Write styles to override default (dark) mode when light mode is enabled
• Create a light theme for view types
• Add Light/Dark toggle to dashboard controls
• @121watts did some cleanup

• CHANGELOG.md updated with a link to the PR (not the Issue)
• Well-formatted commit messages
• Rebased/mergeable
• Tests pass
• http/swagger.yml updated (if modified Go structs or API)
• Documentation updated or issue created (provide link to issue/pr)
• Signed CLA (if not already signed)

[russorat]

@sanderson FYI

[sanderson]

Is this for dashboards only or the UI as a whole?

[alexpaxton]

@sanderson just dashboards for now. In our user research we learned that light mode was most useful for getting screenshots of a dashboard for use in presentations, or when the dashboard is on a wall mounted display

[ebb-tide]

I'm confused why we have a separate state for determining the current page- isn't it available via router path?

[alexpaxton]

@121watts I talked to @ebb-tide about our approach here a bit, and we concluded that it's unnecessary to have currentPage stored in persisted state. What do you think about moving it to ephemeral or somewhere else?

[ebb-tide]

I understand that the route (url) is a proxy for whether the dashboards component is mounted, so tracking currentPage state and route state is somewhat equivalent. But I don't see why currentPage state should be persisted to local state. Should it be in redux instead? What do you think @121watts ?

[121watts]

@ebb-tide we don't need to persist the currentPage to local storage. It can be stored in memory, specifically the redux store.

[ebb-tide]

👍 thank you!

[ebb-tide]

👍