[Stack monitoring][Angular removal] Tech debt

[estermv]

This issue is to keep track of the tech debt that we want to take after the migration is complete.
At this moment is just a collection of raw notes that I kept while working on it.

• [Stack monitoring][Angular removal] Add unit tests #121149
• [Stack monitoring][Angular removal] Refactor global state #121150
• [Stack monitoring][Angular removal] Remove external config context #121151
• Re-write setup mode (@jasonrhodes to link up a larger track of work around setup mode UX here)

[elasticmachine]

Pinging @elastic/logs-metrics-ui (Team:logs-metrics-ui)

[matschaffer]

I removed "Use time from date time picker: We are using the time from kibana.services.data.query.timefilter.timefilter that is not automatically synced with the datepicker. " which should be fixed by #112063

[matschaffer]

@jasonrhodes this has come up near the top of "Ready" but it feels way to large to work on as-is.

I'm guessing each of @estermv 's notes could be an issue on their own. "Re-write setup mode" feels like an epic really.

@estermv or @jasonrhodes what would you recommend as a good "do first" from this issue, if anything?

[matschaffer]

Actually, the above has me thinking this should really be in "refining" so I moved it there for now.

[estermv]

This definitely needs to be refined, this issue was opened before I went on PTO just to keep some notes about things that should be done after the migration, but it's just my opinion. Is up to the team to decide if this makes sense or you just want to close the issue.

I'll add more details to the description between today and tomorrow, so it's easier to decide if it's something worth working on or not.

[jasonrhodes]

Thanks for the ping, @matschaffer -- let's convert this to type: Epic and then create implementation tickets for individual pieces that are actionable, and connect them here using the - [ ] link-to-ticket format. @matschaffer would you mind taking the lead on refining this and pulling in Ester, Philip, Sandy, or whoever else may have context here to help get those implementation tickets created? Once we do that, we can pull in a few of them at a time per cycle.

[smith]

Closing this. See #127224 instead.