Move name and description into a getter function

[alexstandiford]

It would probably be best if name and description were put in a getter method. Most plugins want to translate these, and we shouldn't force all implementations to set these up when they're not used in most-cases.

[alexstandiford]

It would be best to use the __get magic method in classes that use translation strings, instead of setting these in the constructor.

This would prevent a refactor across sites, and allow us to benefit from PHP's own methods to do this, anyway.

EDIT

It won't be this simple because description and name are public, and we don't have the context for the translation strings.

For now, unfortunately, we probably have to just leave it as it is and think deeper on how this can be handled better.

[alexstandiford]

The key motivation for putting these in a getter method is to make them translate-able without running the constructor. Related to #36.

Perhaps the string is untranslated if you access the value directly, and there's some way baked into the trait to handle one-time translating of these items if a specific getter method is called?

[alexstandiford]

underpin::__ is now a method, and these items can be translated programmatically without a constructor, so adding this to a __get method should work nicely.