BHV-14030: Refactor/Optimize ExpandableText.less. Enyo-DCO-1.1-Signed-of...

...f-by: Brooke Peterson <brooke.peterson@lge.com>

###Summary
This PR moves the '.moon-body-text' class directly onto the moon.ExpandableTextButton, so we do not need to use it as a mixin class in the namespace class ('.moon-expandable-text-button').

###Detailed Notes:
1. Moon.ExpandableText already has the text class defined on its client {name: 'client', classes: 'moon-body-text moon-expandable-text-content'}. This is the property way of doing so.
2. In the existing code, moon.ExpandableTextButton used a '.moon-item' class which brings in 'moon-sub-header-text" properties, then use '.moon-body-text' as a mixin class in the '.moon-expandable-text-button' to override the '.moon-sub-header-text' properties. This is not efficient. If we put the '.moon-body-text' directly onto the moon.ExpandableTextButton, and adjust the padding/spotlight bg color in '.moon-expandable-text-button', we do not need the override mixin class and no need to worry about RTL.
3. Using text class directly onto the widget not only reduce lines of css code but also will help performance as switching from view to view these common text classes are cached.

###Test Performed:
Desktop Chrome Version 37.0.2062.124
Master 688 nfs build side loading