This PR adds default permissions to application commands.

NOTE: I've opted to go this route because *bool is awkward to work with, especially since these are usually made inline in a struct. With this implementation, users who want the (Discord) default can just not set it at all.

It also removes SlashCommand, because it wasn't used anywhere and was a dupe of CreateCommand

This PR adds some formatting helpers from https://discord.com/developers/docs/reference#message-formatting

I think these will be useful for responding to interactions, etc. without having to look up reference docs every time.

As you can see in the examples, this allows users to group common parts of a router. The indentation is nice for visual grouping, and it can help reduce re-typing the common prefix.

Adds a Message() Message method to the embed builder.

Only exists for the sake of convenience, similarly to InteractionRespData() *InteractionRespData

A new type for incoming interactions, also attaches the http.Request.Context to it.

This helps us not muddle up the Discord types for the sake of the router.

Currently most format's signatures accept strings, however, when formatting a user object for example, we are most likely to be using a snowflake.

I think we should change those signatures.

As an example, there is https://github.com/Karitham/corde/blob/b03180c5b02dce529e51035ea226c058f72c1b13/0_example/todo/todo.go#L58

Which would benefit from just taking in a Snowflake.

We could also take in any, and check for string, fmt.Stringer or use fmt.Sprint, but I'm not exactly sure how that'd end up looking

Builders are currently a mess, and you even have to call B() at the end to build the embed/response.

We should be able to make corde's embed/responses actual builders themselves, and we wouldn't have to rely on yet another type.

Currently, there's very little tested on the main functionality.

With #7 landing, we should be able to make basic integration tests extremely easily, and as such, try to cover more of our API

I added comments to most (if not all) exported things.

Most of the comments are basic, but at least it will look a bit better on godoc.

Also corrected the spelling for Attachements -> Attachments, which is breaking (but should be done sooner than later imo)

As an aside, I'm not sure I like the name Validate.

It seems like Verify makes more sense, and even then maybe moreso in a middleware package.

Either way, this PR adds some tests for said middleware.

We need to make sure all the API types are correctly fleshed out, with the correct struct tags & pointers, as to meet discord's API definitions.

owmock's types are basically there, but they're not exactly implemented in the library.

We also need to map the rest of the API, but this is a long and boring task, which can be done on the go

Middlewares are lovely.

They're useful for all kinds of stuff, and they're especially useful when accompanied by a great routing library.

We need to figure out a nice design to apply middlewares to Routes, Groups and Subroutes. Chi does this amazingly well