feat: cluster::interaction_followup_get_original

[Mishura4]

This PR adds a method for the Get Original Interaction Response API endpoint, which is quite essential in order to use raw interactions. It also adds interaction_response_get_original as an alias for it, similar to interaction_response_create. Also adds sync and coro methods for both.

[netlify]

✅ Deploy Preview for dpp-dev ready!

Name	Link
🔨 Latest commit	a98aa52
🔍 Latest deploy log	https://app.netlify.com/sites/dpp-dev/deploys/64ab4869e10fbb0008079016
😎 Deploy Preview	https://deploy-preview-723--dpp-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[braindigitalis]

doesnt this do what get_original_response already does?
there are so many interaction endpoints, i get confused.

[Mishura4]

Yes, from dpp::interaction_create_t ; however this is similar to the cluster::interaction_followup_edit_original() that already exists, which is the same as dpp::interaction_create_t::edit_original_response.

Having a method on the cluster notably allows for sync and coro convenience calls ; for example with PR #724 one can do co_await cluster->co_interaction_get_original(event.token) instead of co_await dpp::awaitable{event, &dpp::interaction_create_t::get_original_response}

[raxyte]

There is no such thing as "original followup" in the API.

[Mishura4]

So then should we remove cluster::interaction_followup_edit_original which is currently already in the lib?

Or leave it but only add interaction_response_get_original?

[Commandserver]

Im for removing the old interaction_followup_edit_original

[Commandserver]

It's more confusing than helpful having this duplication anyway

[raxyte]

So then should we remove cluster::interaction_followup_edit_original which is currently already in the lib?

Sure. I think it might have been meant to be interaction_response_edit_original or similar, instead of followup.

[braindigitalis]

we can't just remove it, things are using it.

it would have to be deprecated, but there is a reason it's called "original":

https://discord.com/developers/docs/interactions/receiving-and-responding#followup-messages

the API endpoint contains the string "@original". it was originally called the "original response" and was renamed to "initial response". both mean the same thing.

definitely do not delete!

[braindigitalis]

also it's in the API docs section about follow up messages.

the API docs on interactions are a mess.

[raxyte]

That is not a followup message. Followup endpoints are at the bottom of the page.

Also, there is nothing using that function inside DPP.