Minimal permissions for 'spo miscellaneous' 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 knowledgehub get
• m365 spo knowledgehub remove
• m365 spo knowledgehub set
• m365 spo orgassetslibrary add
• m365 spo orgassetslibrary list
• m365 spo orgassetslibrary remove
• m365 spo orgnewssite list
• m365 spo orgnewssite remove
• m365 spo orgnewssite set
• m365 spo search
• m365 spo set
• m365 spo userprofile get
• m365 spo userprofile set

Use the listed spo command entry points as the scope, and read the linked writing and minimal-permissions guidance first. Review each command's documentation and add a Permissions section before Examples, ordering multiple resources alphabetically and documenting only the minimal supported delegated or application permissions. Verify all 13 listed commands follow the provided examples.