Add a MUST statement preventing 2 entries from having the same statusPurpose

[PatStLouis]

It would be advisable to prevent issuers from including 2 entries with the same statusPurpose. Or at the very least say that if 2 same purposes are included, each entry MUST have an id field.

Is there use cases where an issuer might want to provide 2 separate revocation entries? I could see it being a thing, however there needs to be a way to differentiate them both based on a unique id.