Add Collection as a Policy Evaluation Expression

[bmg13]

Feature Request

ℹ️ This issue is a result of the feedback obtained described in here.

Which Areas Would Be Affected?

This Feature proposes the possibility of having Collections as rightOperand in Policies.
As an example, for creating a Policy with a constraint to match if the groups a BPNL is assigned are allowed to fetch the respective catalog, the rightOperand could be something similar to the following

"constraint": 
{
	"leftOperand": "tx:BusinessPartnerGroup",
	"operator": "isAllOf",
	"rightOperand": ["some-group-1", "some-group-2"]
}

Instead of having to contain a comma-separated String as an only option (for this scenario).

Why Is the Feature Desired?

To allow to have a more broad use of different types, specially Collection.

Solution Proposal

Create a new Expression implementation to include a Collection as well.

[github-actions]

Thanks for your contribution 🔥 We will take a look asap 🚀

[jimmarino]

This is not something trivial to support, given the ambiguities associated with Json-Ld. See #4525. It would require significant time to investigate. The current string-based approach can support the requirement, so I don't thing this will get very high priority.

[github-actions]

This issue is stale because it has been open for 14 days with no activity.