Execution context remains the same on every route change

[eokoneyo]

Kibana version:
main (8.15)

Describe the bug:

This issue was reported by on slack, it seems the pageName in the execution context remains the same on every route change. Ideally the on route change the we should set the values of the execution, this typically includes pageName, alongside couple of other values. On investigating this it seems the implementation to gather the details for the current page's context does exist, however it doesn't get persisted to the execution context instance because it's also undefined within said implementation, hence why subscribers receive a stale value

Steps to reproduce:

1. Open up the use_execution_context.ts file, add in the following

console.log('executionContext:: %o , context to update:: %o \n', executionContext, context);

2. on navigating through pages in app, we'll consistently notice that the value for execution context instance is undefined, with context value actually updating.

Expected behavior:

• Context value computed on route change should be persisted to the execution context instance of the app

[elasticmachine]

Pinging @elastic/appex-sharedux (Team:SharedUX)

[Dosant]

My guess is that this got broken when we moved the sharedux router to packages (a while ago). We probably lost context that was picked up from kibana_react. The fix should probably be to add this context to KibanaRenderContextProvider and use it from there. This only be fixed for
the places that use the provider

[Dosant]

I took a look, I believe this is the context, hope I got it correctly:

• There was a useExecutionContext hook in kibana_react to set current application context for logs / apm etc
• Instead of calling it manually security solution team implemented a custom wrapper arond react router's Route component that sets the context [Security Solution] Propagate execution context #131805
• In that PR an idea was discussed about making this custom component shared across Kibana [Security Solution] Propagate execution context #131805 (review)
• Later we extracted that Route component to a package (without deleting the original implementation in kibana_react yet) [Shared UX] Migrate router from kibana react to shared ux #138544
• And then replaced most of the react-router Route usages and Route from kibana_react with it [Shared UX] Adoption of Shared UX Route component  #150357
  • Unfortunatly, it looks like the execution context didn't work from the Route from the package because context wasn't provided. This means that useExecutionContext calls from [Security Solution] Propagate execution context #131805 became broken and all the new usage that were supposed to be calling useExecutionContext with the new Route component. I believe this issue wasn't really "completed" Implement a generic solution to execution context propagation inside Kibana #132629

So atm and for quite a while, I believe, only the places where we explicitly call useExecutionContext from
import { useExecutionContext } from '@kbn/kibana-react-plugin/public'; or executionContext.set directly correctly set the execution context