Use callback filtering with Gurobi 13.0

[simonbowly]

Gurobi 13.0 adds GRBsetcallbackfuncadv to the C API, which is equivalent to GRBsetcallbackfunc but allows the caller to select only some where codes and disable the others. The major advantage is the ability to filter callbacks the user doesn't need in compute server environments to reduce communication overhead.

Since Gurobi.jl always adds the callback to make interrupts possible (is think?), using wheres=(1<<GRB_CB_POLLING)|(1<<GRB_CB_MESSAGE) if there is no user callback coming from JuMP should be a nice improvement for remote solves.

See: https://docs.gurobi.com/projects/optimizer/en/13.0/reference/releasenotes/changes.html#specify-where-flags-for-callbacks

[simonbowly]

The other case to consider is to map from the selected JuMP callback types to the where codes actually needed, and select only those (e.g. enable MIPNODE and MIPSOL only if the user has a lazy constraint callback). Not sure if that's easy/possible to collect before the solve starts though.

[odow]

@simonbowly what's the reason for this note. Seems pretty at odds with the premise of the function?

Even if the POLLING bit is not set in the wheres bit vector, the callback may still be invoked with where set to that value