Consider `implements MyInterface` syntax

Would we want this?

module Notifier
  interface!

  # ...
end

class SlackNotifier
  implements Notifier # ✨
  
  # ...
end

The implementation would literally just be Module.alias_method(:implements, :include)

Pros:

1. Reads really nicely, feels native
2. Tools can instantly know that Notifier is an interface, without needing to resolve it first (it likely lives in another file)

Cons:

1. Would need special support in Rubydex/RubyLSP. It wouldn't be understood by other tools by default.
   • Most tools that handle Ruby understand module inclusion, so they'd know the interface's methods become available on the class. They wouldn't know that about this implements keyword without having bespoke support built for it.

Originally posted by @amomchilov in https://github.com/Shopify/type_toolkit/pull/2#discussion_r2850115519

Start with the proposed Notifier and SlackNotifier example and review the referenced Rubydex/RubyLSP compatibility concerns. Determine whether the project should adopt implements as an alias for include, what tool support would be required, and how completion would be validated.