Clean up code to only use the isPlugin approach

We decided to take the isPlugin approach and use the plugin class as the template's plugin.class, instead of using the built-in PropertyFieldPlugin.

Currently the code is in experimental mode and supports both approaches. We also bootstrap 2 different namespaces to be able to test the 2 approaches.

Clean up the code: remove support for the PropertyFieldPlugin approach.