document for all and any aggregate builtins

[tmccombs]

These functions exist but aren't currently mentioned in the documentation. It looks like these lines were at one point in the policy-reference, but were lost in commit bb0d4e2.

I also wonder if it would be worth mentioning using all in the section on Universal Quantification, something like:

no_bitcoin_miners_using_all :=  all([(app.name != "bitcoin-miner") | app := apps[_]])

[anderseknert]

They have been removed from the docs since they are both considered deprecated.

any can easily be replaced by just checking for set membership, or using the new in operator.
all can be replaced in a couple of ways, like converting to collection to set and check for {true}, and once the every keyword lands in OPA, we'll have an even more powerful way of checking for all conditions.

[tmccombs]

I see. Why not include them, but say they are deprecated?

[anderseknert]

@tmccombs yeah I suppose that would be an option, though there's probably a higher chance of people still using them if we did. They are still included if you browse older versions of the docs though.

The PR that had them removed is here btw.