Make Generic Provides Changes Backwards Compatible

[SentryMan]

Upon experimentation, it seems the Class<?> to Type changes we've made are backwards incompatible. Breaking every single multi-module project/plugin library based on avaje is pretty cringe so this PR makes everything (mostly) backwards compatible.

• Reverts changes to Module/Plugin classes and adds deprecation notices
• Creates super classes based on Type for the sake of compatibility (for whatever reason this works)
• renames PropertyRequiresPlugin
• modifies scope builder, generator, and maven plugin to service load the new interfaces

Requires avaje/avaje-spi-service#18 and also will eventually care of #559

[rob-bygrave]

IMO you gotta stop including multiple changes into a single PR like this. It generally is a pain to review and becomes an all-or-nothing merge and reduces the ability to revert individual changes etc in the future.

In addition imo you have to try and honour the existing code format. Making format changes only for the sake of code format changes increases the diff and makes more work for me.