Add client state to coredump

[dshaw]

This issue extends #1573 and captures the details needed to complete the implementation.

Client state needed to understand the state of the modeling-app front end is contained within several singletons and xstate machines. Most of the entries in coredump so far have been relatively flat. None of these will be flat and some might have arbitrary structures. Some state might need to be excluded in the dump, like TOKEN in Auth. For excluded data that’s provides critical insights into whether the app should be functional, we may want to include a data validation like isValidToken: boolean.

Proposed structure

"client_state": {
    "kcl_manager": {},
    "scene_infra": {},
    "engine_command_manager": {},
    "modeling_machine": {},
    "settings_machine": {},
    "auth_machine": {},
    "home_machine": {},
    "command_bar_machine": {}
  }

[dshaw]

Uses #2316 as a part of its test fixture.

[dshaw]

Add fileMachine.