Discord interactions

[Acnologla]

Description

This pull request adds discord interactions gateway interface.

Example:

func interaction(session disgord.Session, evt *disgord.InteractionCreate) {
    if evt.Type == disgord.InteractionMessageComponent {
        if evt.Data.CustomID == "click_one" {
            txt := fmt.Sprintf("User %s clicked in the button %s", evt.Member.User.Username, evt.Message.Components[0].Components[0].Label)
            err := disgord.SendInteractionResponse(evt, &disgord.InteractionResponse{
                Type: disgord.ChannelMessageWithSource,
                Data: &disgord.InteractionApplicationCommandCallbackData{
                    Content: txt,
                },
            })
            fmt.Println(err)
        }
    }
}
func main() {
    client := disgord.New(disgord.Config{
        BotToken:     "token",
    })
    defer client.Gateway().StayConnectedUntilInterrupted()
    client.Gateway().InteractionCreate(interaction)
}

Type of change

Please delete options that are not relevant.

• [ ] Bug fix (non-breaking change which fixes an issue)
• [X] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Benchmarks

If this PR requires benchmarks (say it is an very dependent component or takes a lot of resources/use, use pprof if you need to) then the benchmarks are provided before and after such that we can make logical decisions. Note that if you add a benchmark and find your solution to run slower, the code might still be valuable so your results are welcomed anyways! If no benchmarks are needed, feel free to delete til paragraph.

Checklist:

• [X] I ran go generate
• [ ] I have performed a self-review of my own code (remember to run go fmt ./...)
• [ ] I have commented my code, particularly in hard-to-understand areas
• [ ] I have made corresponding changes to the documentation
• [ ] I have added tests that prove my fix is effective or that my feature works
• [ ] New and existing unit tests pass locally with my changes
• [ ] Any dependent changes have been merged and published in downstream modules
• [ ] Added benchmarks if this is a performant required component (potential bottlenecks)

[andersfylling]

Looks good! I have one request that needs to adjusted, but besides that it's all clean.

[andersfylling]

While you might see methods looking like this, some can easily be converted.

REFACTORED - I guess something like this is how it would look for your case