[Security Solution] Switch from core redux create store to the one provided by redux-toolkit

[kqualters-elastic]

Some of the least stable parts of security solution involve data fetching hooks, and how those async events/data are managed in state in the application as the request is made/pending/complete. To fix this, security solution store will make use of redux-toolkit's configureStore, and thunk middleware to make requests, initially around timeline, but possibly more parts of the app. This will give more control and make the data fetching logic easier to test, as well as give some of the other benefits of configureStore, immr to potentially help performance, and some middleware that will flag action payloads or parts of state that end up containing things that should not be there due to size (can be bad for performance in dev or prod) or unserializability (generally only a problem in dev, but still not something we should do).

[elasticmachine]

Pinging @elastic/security-threat-hunting-investigations (Team:Threat Hunting:Investigations)

[elasticmachine]

Pinging @elastic/security-threat-hunting-explore (Team:Threat Hunting:Explore)