Adds command viva engage community user list

[Jwaegebaert]

Closes #6295

In this PR, I've added a new custom method to our zod setup. This method allows us to define 'enums,' or a list of options for a specific command, which zod will verify in a case-insensitive manner. Dropping in favor of #6373

[MathijsVerbeeck]

Hi Jasey,

Command works great. Something that I've noticed is that if we for example have a user that is both a "Admin" and a "Member", we will see the record appear twice in the output, once with the property "roles": ["Member"] and once with roles: ["Admin"]. Is this something that we perhaps could finetune?

[Jwaegebaert]

Something that I've noticed is that if we for example have a user that is both a "Admin" and a "Member", we will see the record appear twice in the output, once with the property "roles": ["Member"] and once with roles: ["Admin"]. Is this something that we perhaps could finetune?

I don’t think this behavior is too bad. It seems logical for users to appear twice if they have two different roles. I’m not sure how we handle this with other commands, but I think it’s okay to keep this behavior.

[MathijsVerbeeck]

Something that I've noticed is that if we for example have a user that is both a "Admin" and a "Member", we will see the record appear twice in the output, once with the property "roles": ["Member"] and once with roles: ["Admin"]. Is this something that we perhaps could finetune?

I don’t think this behavior is too bad. It seems logical for users to appear twice if they have two different roles. I’m not sure how we handle this with other commands, but I think it’s okay to keep this behavior.

All good, just wanted your opinion. Thanks for the clarification.

[MathijsVerbeeck]

Thanks for the PR Jasey. In the future, could you please make sure that your commit message contains the link to the correct issue? :-)