Reduce augmentation handling duplication in generated implementations

Our builder-based implementations usually end up implementing Augmentable contract with the related baggage of a field and augmentation() implementation.

Since the contract is generic and immutable, we can easily concentrate this support into a base superclass – thus reducing the amount of code we generate and also drop the number of augment() implementations.