Minimal permissions for 'spo sitedesign' 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 spo sitedesign add
• m365 spo sitedesign apply
• m365 spo sitedesign get
• m365 spo sitedesign list
• m365 spo sitedesign remove
• m365 spo sitedesign set

Start with the linked writing-the-docs and minimal-permissions guides, then review the documentation pages for the six listed spo sitedesign commands. Add a Permissions section before Examples on each page, using the minimal delegated and application permissions, alphabetizing multiple resources and noting auth types where applicable. Done means all six command pages follow the documented format consistently.