Minimal permissions for 'viva engage related' commands

We're adding a new Permissions section to all commands. This section will document the minimal delegated and application permissions required to execute the command.

The goal is to:

• Make it easier to run the CLI with custom app registrations and application permissions.
• Ensure we only document the minimal set of permissions needed.
• Keep documentation consistent by placing the Permissions section right before the Examples section.
• If there are multiple resources, order them alphabetically
• If there are commands that only support one type of auth (like delegated or app-only), we have an example for that as well. E.g. m365 planner tenant settings list - Permissions

Resources

• Writing the docs page
• How to document minimal permissions
• Planner example 1
• Planner example 2

Commands in scope

This issue covers the following commands:

• m365 viva engage community-user add
• m365 viva engage community-user list
• m365 viva engage community-user remove
• m365 viva engage message-like set
• m365 viva engage network list
• m365 viva engage role list
• m365 viva engage role-member list
• m365 viva engage role-member remove
• m365 viva engage search
• m365 viva engage user get
• m365 viva engage user list

Start with the listed Viva Engage command documentation pages and read the writing and minimal-permissions guides, then compare the Planner examples. Add a Permissions section before Examples for each command, documenting only the minimal delegated or application permissions and ordering multiple resources alphabetically. Done means all ten commands in scope follow the same structure and auth-specific cases are covered.