Use interaction.createdTimestamp instead of Date.now() in Cooldowns guide section

[Sn4red]

Is your feature request related to a problem? Please describe.

If a user has a different/wrong time, it can cause an error in the cooldown since Date.now() retrieves the current timestamp from the computer where the bot is running, not from the user executing it, resulting in a potential variation in the cooldown.

Describe the solution you'd like

Using interaction.createdTimestamp can solve the problem and would be more informative for the guide, especially if someone tries the code with others.

Describe alternatives you've considered

No response

Additional notes

No response

[almostSouji]

I do not understand the issue, can you elaborate? Timestamps are set and compared based on the same source of truth.