BUG: RuntimeException when Flux elements are nested inside Gridelements

[oli09x]

I have checked that the bug exists in the dev-development branch
Yes

I have checked that there are no already open issues or recently closed issues about this bug
Yes

Describe the bug
When a page on the frontend is opened which contains a Flux element nested inside of a Gridelement (EXT:gridelements), the following error occurs: Unable to resolve a ConfigurationProvider, but controller indicates it is a Flux-enabled Controller - this is a grave error and indicates that EXT: FluidTYPO3.Flux itself is broken - or that EXT:FluidTYPO3.Flux has been overridden by another implementation which is broken. The controller that caused this error was FluidTYPO3\Flux\Controller\ContentController".

To Reproduce
Steps to reproduce the behavior:

1. Create a Grid Element.
2. Create a Flux element inside of that Gridelement
3. Open page on the frontend

Expected behavior
Working page.

Additional context
This error happens on EXT:flux version 10.1.0 and 10.1.1. It doesn't occur on 10.0.10 or lower.

[oli09x]

Used Typo3 version: 12.4.28
Used version of EXT:gridelements: 12.0.0

[NamelessCoder]

If you have access to the Gridelements EAP, please test with that version.

Normally this error is only raised if Flux encounters an incomplete context (cObj, mimic ServerRequest, overridden ConfigurationManager, etc.), which usually only happens when you're rendering the Flux content elements through non-standard means (e.g. when Gridelements is doing the rendering instead of the core itself).

You may also want to test this with dev-development of Flux - there have been some fixes about resolving the content object data in that branch, fixes which aren't yet released.