Add applications.commands.update back as a regular oauth scope

[AnotherZane]

Description:

The oauth scope, applications.commands.update was moved to a client credentials only scope as seen in issue #2443. However, a better alternative would be to add it back as a regular oauth scoped and make it more descriptive during the authorization flow since there are genuine use cases for it.

Why This is Needed:

Registering and managing application commands is more of a one time process, it is not something that developers should really have to write a lot of code for. Discord does not provide developers with a dashboard to manage these commands.

While I do agree with #3302 as well, I do think that this scope would be fine since we have scopes such as applications.store.update.

With the applications.commands.update, 3rd party tools using oauth can be created to assist developers in managing application commands more easily.

Alternatives Considered:

• Use the client credentials grant to get a token with this scope, however this does not really help with the above mentioned purpose.
• Potentially ask for the developers portal to include a brand new application commands dashboard?