Minimal permissions for 'spo site related' commands. Part 2

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 site commsite enable
• m365 spo site hubsite connect
• m365 spo site hubsite disconnect
• m365 spo site hubsite-theme sync
• m365 spo site inplacerecordsmanagement set
• m365 spo site membership list
• m365 spo site sharingpermission set
• m365 spo site versionpolicy get

Read the linked writing-the-docs and minimal-permissions guides first, then inspect the documentation for the eight listed spo site commands. Add a Permissions section before Examples for each command, documenting the minimal delegated and application permissions and ordering multiple resources alphabetically. Done means all commands in scope follow the documented format and include auth-specific examples where applicable.