feat: add wildcard components

[sudojunior]

This extends further from #145 by adding a listener for all components on a message as a wildcard - the component used can be determined by ctx.custom_id.

• Method Docs / Descriptions

Added

• MessageInteractionContext#registerWildcardComponent(message_id, callback, expiration, onExpired)
• MessageInteractionContext#unregisterWildcardComponent(message_id)

Wildcard components use the invoking message ID with an asterisk (*) to prevent possible conflicts with existing registered components.

For context sake, this was implemented with eda121e (Gist Component) with a specific use for ephemeral components (and having it unregister itself immediately before invoking the callback).

[sudojunior]

I could have also added a predicate return on the register method, which would have ended up looking like...

class MessageInteractionContext {
  // ...
  registerWildcardComponent(message_id: string, /* ... */) {
    // ...
    return () => this.unregisterWildcardComponent(message_id);
  }
}

It is already so far against the existing style of the library, but I figured it'd be useful - similar to how I handled it in the demo.

const unref = this.registerWildcardComponent('0123456789', ctx => {
  // check interaction
  unref(); // remove after pre-conditions pass
  // continue
});

[Snazzah]

@sudojunior Sounds good, would have to change the other functions to match.