fix(interactions): DefaultPermission should not be a bool ptr

[Sculas]

DefaultPermission should not be a bool pointer.

You can no longer pass in true or false, it must be a variable and you need to take the address of it. This absolutely makes no sense.

[FedorLap2006]

Thanks for noticing that! I'm going to close this, because it's intentional.

Pointer to bool allows encoder to omit the field, because nil is going to be considered the empty value, instead of false.
The current behaviour of default_permission requires the field to be omitted (nil), when no default permission should be set. Or to be specified (true, false), when default permission should allow/deny usage of slash command without permission overwrite

Just usage of the variable (i.e. just bool), won't work, because if it would be set to false (or not specified when initialising the struct), encoder would omit it, which should not happen.

[FedorLap2006]

Additionally, the same idea is used in #1026. It has *float64 fields to allow json encoder to omit them as well, to not set a max/min value.

[FedorLap2006]

Also, @Lucaskyy, you can read more about this behavious here

[Sculas]

Ah yeah you're right, it's inconvenient but since there's no other way to do this in Go we'll have to live with it :)

[FedorLap2006]

There is a couple of ways, but this one is the easiest, since it requires just one wrapper function.