Type-safe global query system

[sim642]

Queries like WarnGlobal and InvariantGlobal are only used globally in dummy ctx. Moreover, they have Obj.t arguments which are unsafe.
Every analysis lifter which adds its own global unknowns must have special cases for converting such arguments for WarnGlobal and InvariantGlobal. If that is forgotten, then Goblint simply segfaults.

This PR introduces global queries using a separate global_query "transfer" function and gctx global "context" for the queries, which doesn't require all the dummy data.

TODO

• Convert InvariantGlobal query.
• Add documentation.
• Use this for Generate flow-insensitive YAML witness invariants with ghosts for privatized variables #1394.

[michael-schwarz]

Nice! I think we should add this to the documentation.

Also, why is it necessary to stop recording per loop termination information here? I think such information can be very helpful, e.g., when debugging or potentially in the future, when we may want to slice out a program containing only the part for which we could not show termination.

[michael-schwarz]

Could we maybe think of better names for these things? I think ctx and query are things we are overusing already.

Also, WarnGlobal does not really fit into the category query anyway, as it returns unit. Maybe for it, a separate transfer function that does not get a ctx but only an ask and is called per analysis at the end of the analysis would be the more principled thing?

[sim642]

Just ask isn't enough for these kinds of things though, they also need global. For example, the deadlock analysis needs to traverse the entire cycle starting from a global.

[michael-schwarz]

True, maybe give it ask and getg then?