fix(interactions): get info from cache first if available

[Soheab]

Summary

Fixes #605

This PR changes the assignment of the following attributes for Interaction to try cache before constructing the object: .message, .user

This is needed because fields like status are not sent in the Interaction member payload but are usually cached.

Preview:
I don't know how to test .message and User for .user but the correct object is returned.

Checklist

• If code changes were made then they have been tested.
  • I have updated the documentation to reflect the changes.
  • I have run task pyright and fixed the relevant issues.
• 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, ...)

[netlify]

✅ Deploy Preview for nextcord-gh-action ready!

Name	Link
🔨 Latest commit	bcb273b
🔍 Latest deploy log	https://app.netlify.com/sites/nextcord-gh-action/deploys/62bf65b5e8ca4c00086a6999
😎 Deploy Preview	https://deploy-preview-724--nextcord-gh-action.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 settings.

[DenverCoder1]

If not all intents are enabled, there may be some events that don't update the cached message I think.

Is it possible the interaction message will contain data that is newer/more accurate than the cache?

Possibly they may need to be merged together?

[EmmmaTech]

Looks good

[DenverCoder1]

Let me know what you think of these suggestions. This should use the cache, but also update any additional fields provided by the interaction data.

[Soheab]

If not all intents are enabled, there may be some events that don't update the cached message I think.

Is it possible the interaction message will contain data that is newer/more accurate than the cache?

Possibly they may need to be merged together?

If not all intents are enabled, there may be some events that don't update the cached message I think.

Is it possible the interaction message will contain data that is newer/more accurate than the cache?

Possibly they may need to be merged together?

keep forgetting to respond, sorry
But no, I haven't experienced a situation where the Interaction Message was missing information or was out of date, mainly because it's not really used since Interaction has most of the stuff

I just did it for the sake of "why not".

If not all intents are enabled, there may be some events that don't update the cached message I think.

Same as above, I don't know but if that's true but that doesn't sound good and a potential dataloss.

---

Response to the suggestions:

They look good to me, will of course require testing. Will do that when I can, thank you :)

[DenverCoder1]

But no, I haven't experienced a situation where the Interaction Message was missing information or was out of date, mainly because it's not really used since Interaction has most of the stuff

I believe you are correct since if the member/message is cached at all, it should always update in the corresponding update/edit event, so just using the item from the cache should be enough.