Better error checking for BoundaryRestricted objects

[friedmud]

Description of the enhancement or error report

Currently, BoundaryRestrictable objects are checked to make sure their boundary IDs exist... BUT they're checked against both nodesets and sidesets (when they may be restricted to just a single type). This can allow some objects to "slip through" if they are "nodal" and assigned to a nodeset that doesn't exist but a sideset does exist with that same ID (or vice versa). This needs to get fixed up.

Rationale for the enhancement or information for reproducing the error

We should enhance BoundaryRestrictable so that it understands whether the object is being restricted to sidesets or nodesets and can do the appropriate check.

Identified impact

Limited internal API modifications. User developed objects most likely won't inherit directly from BoundaryRestrictable so changing that API shouldn't effect most applications (I'm sure there will be one or two though!)