applications.commands.read scope

[advaith1]

Description
The restriction of the applications.commands.update scope to the client credentials grant broke a feature I made that displayed a list of bots' slash commands on a webpage. Since my use case only involved reading and not editing, it would be useful to have a read-only command scope that is available in standard OAuth. I don't think read-only access would be a security risk since it is info accessible by any user.

Why This is Needed
Applications using the update scope to read commands were suddenly broken with no replacement. This would make that functionality possible again without the security issue.

Alternatives Considered

• Allow GET /applications/:id/commands for other applications #2337 (closed)
• Un-restrict the update scope and add more details about it in the authorize screen, and maybe a warning in the dev portal scope picker so people stop selecting it by accident (Add applications.commands.update back as a regular oauth scope #3449)

Additional Details
Issue discussed in DDevs earlier