enh(Contexts): set active navigation entry

[blizzz]

This is sort of a PoC actually. Addresses #933

I looked at the backend options first. The problem is that we are currently working with a set anchor, i.e. example.com/index.php/apps/tables/#/application/28, so that is no information that we have on the backend. We'd either have to change this behaviour, or to avoid completely reloading the Tables app, having a mechanism that works with both, an URL that can be understood by the server, and the inside-app URL with the anchor.

Nevertheless, I looked at the frontend bits for a quick win. And there is the quick win:

Screencast_20240430_113348.webm

It is not ideal though, because

• the active entry is visible flicking from Tables to the Tables Application when opening the Application directly, as it is initially set by the backend, and later adjusted by the app
• there is no exposed API to manipulated the navigation bar, so I am directly manipulating the JS class. This will easily break. It might be an approach to serve NC 29, but for 30 some API by the server would be necessary. Even if the backend scenario is solved, as laid out up front, this will be needed for inside-app Application switches.

What do you think?

[blizzz]

Rebased to resolve conflicts.

While I'd only consider that a workaround, i think this is good enough for now.

Definitely not more than a workaround, that's what i tried to say :)

[blizzz]

@juliushaertl keep it for 0.8 or also bring it down to 0.7?

[blizzz]

/backport to stable0.7