Bugfix for sparse QoI constraint cases
Bugfix for sparse QoI constraint cases

The undefined behavior here actually passed tests for me originally, but
is currently causing segfaults in a few GRINS tests.  This fixes them.

libMesh/libmesh,jwpeterson/libmesh,BalticPinguin/libmesh,libMesh/libmesh,BalticPinguin/libmesh,jwpeterson/libmesh,libMesh/libmesh,roystgnr/libmesh,dschwen/libmesh,jwpeterson/libmesh,dschwen/libmesh,dschwen/libmesh,jwpeterson/libmesh,roystgnr/libmesh,roystgnr/libmesh,roystgnr/libmesh,dschwen/libmesh,jwpeterson/libmesh,libMesh/libmesh,dschwen/libmesh,BalticPinguin/libmesh,roystgnr/libmesh,BalticPinguin/libmesh,libMesh/libmesh,dschwen/libmesh,roystgnr/libmesh,dschwen/libmesh,libMesh/libmesh,BalticPinguin/libmesh,dschwen/libmesh,BalticPinguin/libmesh,roystgnr/libmesh,BalticPinguin/libmesh,jwpeterson/libmesh,roystgnr/libmesh,libMesh/libmesh,jwpeterson/libmesh,jwpeterson/libmesh,libMesh/libmesh,BalticPinguin/libmesh