[Monitoring] Remove angular dependency from Stack Monitoring

[igoristic]

AngularJS will no longer be supported, context here: #90145

We need to investigate what it would take to completely remove angularjs (and its rough timeline). Currently our plugin relies on angularjs (sorted by most complex order) for:

---

- Directives

SM is currently wrapped in a pretty large angular directive, example. This will probably be the hardest and the most time consuming thing to port over to react. This will involve breaking things down into their own components and decoupling any global relationships/dependancies

---

- Routing/Navigation (with passing url params as state to routes)

Routing in angular is very different than in react. The first step would probably involve changing all our angular route controllers (that are used inside .when()), and their respective html views into react components, and the next step would be to only render our whole app (from react-dom) once (instead of the individual components)

Possible alternative:

• react-router-dom
• Implement a simple react useContext with our current GlobalState class in url_state.ts

---

- Breadcrumbs

This hooks into kibana's top nav header, and we have full control over it (so should be pretty straight forward)

Possible alternative:

• Convert the current angular provider into a hook/context in react
• Construct breadcrumbs based on the current URL (rather than on the fly). This could be incorporated into our routing hook

---

- Timefilter refresh execution

This just updates angular's scope digestion along with anything else we put into executor.register which is an event interval from EuiSuperDatePicker

Possible alternative:

• Use a react hook that would be triggered in onRefreshChange by EuiSuperDatePicker

---

There are couple of other things that I don't think are worth a mention since Kibana's NP core features has the alternatives we need

[elasticmachine]

Pinging @elastic/stack-monitoring (Team:Monitoring)

[jasonrhodes]

Replaced by #109791