Allow for Multivalue Attribute to Be a Subconfig Setting

How: example we want to build subconfigs based off of our broad and narrow attributes on the item level but it is not available to select, only non-multivalue attribute options appear.

Why: multivalue attributes are highly used

For Who: carters inspire users

Impact: build subconfigs based off of broad and narrow category attributes (ex. tops, bottoms, etc.)

Additional context:

Please, add your suggestion and feedback above to add to the insights used by Product team when deciding priorities and direction of the Inriver PIM.