Add Test Suite and 'Subpixel Rendering' Profile

Primarily, this adds test suite -- 96b8655b05203842e16f76efd4c64bfbea2f172c plus implemented suggestions by Josef Reidinger and Martin Vidner and more or less important improvements meet by chance.

Subpixel-rendering profile was added and user is warned in case subpixel rendering is requested but FreeType2 without subpixel rendering support is installed. This coerces adding FreeType2 library binding to be able to ensure that installed library has not subpixel rendering compiled in.

Resolved small usability problems:
1. Module doesn't crash during read when some of PREFER_*_FAMILIES is not set in sysconfig file (issue #2). 
2. Module uses values from 'Default' profile when some value do not exist in the sysconfig file.
3. Module doesn't raise error when non-root user is attempting to run fonts-config. Instead, immediately after clicking 'Ok', error popup is shown and whole saving & applying setting section is stoped.

There is last item left unimplemented from suggestions from the last pull request: FontsConfigState feels like a structure, but it is defined as object. It is because of its nature .. it is just an image of /etc/sysconfig/fonts-config, i. e. container of variable values. It can be as whole read from or written in the sysconfig file or loaded, again as a whole, from one of the preset. There's no any aditional logic, so accessors for individual values used by GUI elements should not do any harm, as far as I can see. Of course, when some problem arises, I'll consider the rewrite to a structure immediately.
On Thu, Oct 23, 2014 at 09:01:57AM -0700, Josef Reidinger wrote:
> In test/fonts-config-state_spec.rb:
> 
> > +describe FontsConfig::FontsConfigState do
> > +  include Yast
> > +
> > +  def preset_loaded(fcstate, preset)
> > +    dp = FontsConfig::FontsConfigState::PRESETS[preset]
> > +    return fcstate.fpl == dp["fpl"] &&
> > +           fcstate.search_metric_compatible == dp["search_metric_compatible"] &&
> > +           fcstate.really_force_fpl == dp["really_force_fpl"] &&
> > +           fcstate.force_aa_off == dp["force_aa_off"] &&
> > +           fcstate.force_aa_off_mono == dp["force_aa_off_mono"] &&
> > +           fcstate.force_ah_on == dp["force_ah_on"] &&
> > +           fcstate.force_hintstyle == dp["force_hintstyle"] &&
> > +           fcstate.embedded_bitmaps == dp["embedded_bitmaps"] &&
> > +           fcstate.all_ebl == dp["all_ebl"] &&
> > +           fcstate.lcd_filter == dp["lcd_filter"] &&
> > +           fcstate.subpixel_layout == dp["subpixel_layout"]
> 
> this is quite fragile test as it tests trivial assignment and depends on
> attributes which are set.

@jreidinger
Which other way I should check if given fcstate has some preset
loaded?