Throw error if ordered unsafe to use

[sethaxen]

As noted in #220 (comment), ordered(d) does the incorrect thing unless d is unconstrained. This PR adds a check that throws an error if this is not the case. Note that examples like this will now error even though they are fine to use with ordered, since they don't return a Identity bijector:

julia> bijector(Product(fill(Normal(), 5)))
Bijectors.TruncatedBijector{1, Float64, Float64}(-Inf, Inf)

julia> bijector(Product([Normal(), Cauchy()]))
Bijectors.TruncatedBijector{1, Vector{Float64}, Vector{Float64}}([-Inf, -Inf], [Inf, Inf])

[torfjelde]

LGTM! Though can you bump the patch version?

Also, if you don't use Product but product_distribution (Product is deprecated), it will actually result in a DiagNormal, hence it will work in this particular case. It will still fail for other cases though.

Thanks @sethaxen !

[rikhuijzer]

Uhm for the next time, this should have been a breaking release, no? There could be clients running production depending on the old and broken implementation. They now have to adjust or have no output at all, which means this change is breaking.

[devmotion]

depending on the old and broken implementation.

According to semver, bug fixes are non-breaking. The only problem I see here are the now-failing examples in the OP - but it seems they could be fixed by improved definitions of bijector for product distributions or an improved check that also supports TruncatedBijectors with infinite bounds.