Metro 0.11.0 and MEEPs!

Metro 0.11.0 is out now and it's a fun milestone in Metro's development. Up to this point most of the work in Metro has been focused around the foundation, interop, and frankly feature parity. It's in a really good place on that front now!

Now, Metro will try to push the envelope and explore more advanced and new features. It's done a little of this prior to now, like dynamic graphs.

To broaden input on these proposals, I've set up a dedicated section in the Metro repo's discussions for what I'm calling MEEPs. It's a tongue-and-cheek reference to Kotlin's KEEPs, but notably the P stands for proposal rather than process. There is no formal process here, just trying to create good avenues for soliciting community feedback and ideas 🫡. MEEPs can only be authored or promoted by myself or future maintainers, as they are planned features and not feature requests.

The first three (!!) MEEPs are implemented in 0.11.0 too!

[MEEP-1826] @Assisted parameters now rely on matching parameter names.
[MEEP-1770] Allow use of () -> T as Provider types.
[MEEP-1769] Introduce @GraphPrivate API.

There's also the whole host of the usual bugfixes/improvements, as well as some promoted features and behavior changes!