feat(InteractionResponse): createdTimestamp

[BenjammingKirby]

Please describe the changes this PR makes and why it should be merged:
InteractionResponses have IDs, we can just destructure it and get createdAt and createdTimestamp, (it's a getter because other such properties on other classes were getters)
Close #8916
Status and versioning classification:

• Code changes have been tested against the Discord API, or there are no code changes
• I know how to update typings and have done so, or typings don't need updating
• This PR changes the library's interface (methods or parameters added)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

2 Ignored Deployments

Name	Status	Preview	Updated
discord-js	⬜️ Ignored (Inspect)		Dec 14, 2022 at 9:33PM (UTC)
discord-js-guide	⬜️ Ignored (Inspect)		Dec 14, 2022 at 9:33PM (UTC)

[MaksiRose]

As far as I know, createdTimestamp is normally a normal property rather than a method. Is there a reason this is different here?

[imranbarbhuiya]

This isn't a method but a getter that behaves like a property but u can return result dynamically

[BenjammingKirby]

This isn't a method but a getter that behaves like a property but u can return result dynamically

I have no idea why though, as I mentioned, this is a getter because the other .createdTimestamp/createdAt I've seen have been getters, I don't think there's any need for it to be? since the ID is constant

[imranbarbhuiya]

using property will store the Date and number in memory and using getter, it'll generate when needed without storing. Ig this is the reason for not using property but not sure tho

[Qjuh]

using property will store the Date and number in memory and using getter, it'll generate when needed without storing. Ig this is the reason for not using property but not sure tho

That, but also that it doesn’t have to be calculated at all if it isn’t used.