Minimal permissions for 'viva engage message' 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 message add
• m365 viva engage message get
• m365 viva engage message list
• m365 viva engage message remove

Start with the linked writing-the-docs and minimal-permissions guides, then open the documentation pages for the four listed viva engage message commands. Add a Permissions section before Examples, document minimal delegated and application permissions, and order multiple resources alphabetically; completion means all four pages follow the referenced examples.