Since reservations are handled independently (and in parallel), it is
difficult to handle conflicts in a pleasing way at the Portal in the
context of a reservation group. So modify the cluster advertisement
to include the conflict list (we already save a lot of stuff about the
nodes on every cluster, at the Portal) so we head off attempts that
include a conflict, much earlier, and present a nicer error to the user.