Inconsistency with application rest command arguments

[mplatypus]

There is an inconsistency with the positions of application command functions in rest.py. It seems that most functions have an order, like guild, channel, message, etc, but these functions seem to not follow that order, or any of that fact.

I feel that either the guild or the application should be at the top, and the command should be at the bottom, as its the "smallest" in a relative sense.

Functions that I can see that have this ordering inconsistency:

• hikari/hikari/impl/rest.py

  Line 3787 in 3604cec

  async def fetch_application_command(

• hikari/hikari/impl/rest.py

  Line 3818 in 3604cec

  async def fetch_application_commands(

• hikari/hikari/impl/rest.py

  Line 3943 in 3604cec

  async def set_application_commands(

• hikari/hikari/impl/rest.py

  Line 3960 in 3604cec

  async def edit_application_command(

• hikari/hikari/impl/rest.py

  Line 3997 in 3604cec

  async def delete_application_command(

• hikari/hikari/impl/rest.py

  Line 4013 in 3604cec

  async def fetch_application_guild_commands_permissions(

• hikari/hikari/impl/rest.py

  Line 4023 in 3604cec

  async def fetch_application_command_permissions(

• hikari/hikari/impl/rest.py

  Line 4036 in 3604cec

  async def set_application_command_permissions(

Personally, I prefer guild, application, command then permissions.

[FasterSpeeding]

For the relevant endpoint methods where guild is at the end of the positional arguments this was done as it is an optional argument. If you pass it you're targeting guild specific commands whereas if you don't it's targeting global commands.
For the permissions endpoint this wasn't relevant as you're always targeting a guild resource (the applied permissions themselves, rather than the actual command)

I do get that these semantics are a bit weird in retrospect (permissions weren't like this at the time) but this seems to stem from discord's own weird semantics where it's always
/applications/{app_id}/guilds/{guild_id}/commands/{command_id}/perms
but then commands can be
/applications/{app_id}/commands/{command_id}
or
/applications/{app_id}/guilds/{guild_id/commands/{command_id}

The only way I can see for making this more consistent would be splitting the command methods (which are implicitly covering two endpoints) into separate methods for guild commands vs global but that seems a bit unnecessary