Upfront validation to flag incompatible commodity constraints

Similar to what we do for availability constraints.

For example, a lower timeslice bound of 20 would be incompatible with an upper annual bound of 10. This sort of thing should be relatively easy to spot at the input validation stage. Currently it would fail at the dispatch stage with an error message saying that commodity constraints are responsible, which is better than nothing, but it would be better to get more specific info upfront