openconfig-bgp-policy: match-as-path-set

[adamsimpson1]

The match-as-path-set container has a match-set-options leaf that uses the typedef providing ANY, ALL and INVERT options. If we assume, as implied by the model, that an as-path-set is a concatenated set of strings, each of which is a regular expression used for AS path matching, then it's hard to understand how ANY, ALL or INVERT logic would be applied, since the regular expression already encodes these notions. I think it can be argued that the common match-set-options should not be applied to as-path-sets.