BHV-12043: Refactor/Optimize Input.less, InputDecorator.less, TextArea.l...

...ess, RichTex.less. Enyo-DCO-1.1-Signed-off-by: Brooke Peterson <brooke.peterson@lge.com>

### Summary:
This PR refactor/optimize Input.less, inputDecorator.less, TextArea.less and RichText.less by moving the text classes directly onto the widgets. In addition cleaning up and replace the search image with icon font.

### Detailed Notes:
1. Move 'moon-body-text' directly onto moon.Input, moon.TextArea and moon.RichText 'moon-divider-text' onto moon.InputDecorator , moon.TextAreaDecorator and moon.RichText instead of using them as the mixin classes. This approach avoids redundantly defining text properties in the widget namespaces classes thus helping reducing moonstone css size, make existing text classes reusable and improve performance.
2. In the current implementation  -- the RichText.less has almost identical properties as TextArea.less, so the same rules are move to TextArea.less. Only Leave the addition three properties of .moon-rich text in RichText.less.
3. Changed the search icon (in input and rich text samples) from image to icon font. Also in the InputSample.js corrected two minor errors (disabled Input field -should be placeholder text instead of value;  disabled TextArea -- placeholder wording should be disabled textarea not input).
4. Removed unnecessary properties in Input,less, InputDecorator.less and textArea,less.
********
5. There is an area of concern. In moonstone-text.less , input and text area tags are defined in enyo-locale-non-latin format, which resulted of non-latin Input and TextArea use font-family: "Moonstone LG Display" instead of the "font-family: "Moonstone LG Display Light" (the counter part of non-latin moon-body-text). I leave as is for existing apps considerations.

### Test Performed:
1. Desktop Chrome Version 38.0.2125.104, check both light/dark themes, latin/non-latin related samples.
2. Side Loading to master 688 nfs, the inputSample looked good.