When implementing #233124, it became obvious that relying on search session ID changing in order to trigger a refetch was a problem. This is because, in order to make the panels inside a section refetch when the controls in the section output filters, we had to ensure that section-targeted control changes caused a new search session ID. However, this had a consequence of making all other panels in the dashboard also refetch, even if their own filters did not change. Not ideal!

The search session ID should be a consequence of fetching - it should not be responsible for triggering the refresh. That way, we can ensure that only global filter changes create a new search session, whereas section-scoped filter changes should just be appended to the existing session.