docs: misc fixes/clarifications

[shiftinv]

Summary

A collection of documentation fixes for things that aren't big enough to warrant their own PRs.
Going to keep this as a draft for a little while; if anyone has further nits, please leave a comment.

Checklist

• If code changes were made, then they have been tested
  • I have updated the documentation to reflect the changes
  • I have formatted the code properly by running pdm lint
  • I have type-checked the code by running pdm pyright
• This PR fixes an issue
• This PR adds something new (e.g. new method or parameters)
• This PR is a breaking change (e.g. methods or parameters removed/renamed)
• This PR is not a code change (e.g. documentation, README, ...)

[EQUENOS]

Thank you for keeping this as a draft! Here're my suggestions:

• <...>Bot.reload_extension docs should clarify the relation with app command sync
• Interaction.edit_original_response should clarify which message will be edited in case of different interaction types (*)

*: for example, if one defers a message interaction response and then calls edit_original_response then the message being edited is the one with the clicked component

[shiftinv]

Thanks for the comment! :>

• <...>Bot.reload_extension docs should clarify the relation with app command sync

Not sure about this, could you explain it a little more? If this is about automatically syncing on cog load/unload then I suppose we should mention it in Bot.add_cog instead.
edit: 5eab532

• Interaction.edit_original_response should clarify which message will be edited in case of different interaction types

There's a fairly basic table here, though I removed the table entirely in #1113 since it was arguably not the best.

[elenakrittik]

If my word costs anything 😁