inverse of NamedTuple transformations from different ordering/superset

[tpapp]

Currrently inverse for NamedTuple aggregators does not accept different orderings or supersets. Eg

julia> using TransformVariables
    
julia> t = as((a = asℝ, b = asℝ));

julia> inverse(t, (a = 1.0, b = 2.0))
2-element Vector{Float64}:
 1.0
 2.0

julia> inverse(t, (b = 1.0, a = 2.0))
ERROR: ArgumentError: keys(transformations) == keys(y) must hold. Got
keys(transformations) => (:a, :b)
keys(y) => (:b, :a)

julia> inverse(t, (a = 1.0, b = 2.0, c = 3.0))
ERROR: ArgumentError: keys(transformations) == keys(y) must hold. Got
keys(transformations) => (:a, :b)
keys(y) => (:a, :b, :c)

This is OK, but the user should be provided with a method to "regularize" NamedTuples (eg user input may mix up ordering).

[devmotion]

IMO this was fixed by #120. On the master branch, the example above gives

julia> using TransformVariables

julia> t = as((a = asℝ, b = asℝ));

julia> inverse(t, (a = 1.0, b = 2.0))
2-element Vector{Float64}:
 1.0
 2.0

julia> inverse(t, (b = 1.0, a = 2.0))
2-element Vector{Float64}:
 2.0
 1.0

julia> inverse(t, (a = 1.0, b = 2.0, c = 3.0))

ERROR: ArgumentError: _same_set_of_names(transformations, y) must hold. Got
transformations => (a = asℝ, b = asℝ)
y => (a = 1.0, b = 2.0, c = 3.0)
Stacktrace:
 [1] throw_check_error(info::Any)
   @ ArgCheck ~/.julia/packages/ArgCheck/D1ZFJ/src/checks.jl:280
 [2] inverse_eltype(tt::TransformVariables.TransformTuple{…}, y::@NamedTuple{…})
   @ TransformVariables ~/.julia/packages/TransformVariables/F49Oe/src/aggregation.jl:394
 [3] inverse(t::TransformVariables.TransformTuple{@NamedTuple{…}}, y::@NamedTuple{a::Float64, b::Float64, c::Float64})
   @ TransformVariables ~/.julia/packages/TransformVariables/F49Oe/src/generic.jl:284
 [4] top-level scope
   @ REPL[7]:1
Some type information was truncated. Use `show(err)` to see complete types.

[tpapp]

Thanks, forgot to close.