AnnotWidget: support 'de facto' tooltip feature

Most pdf readers implement a tooltip feature by
showing the string content of 'TU' field of a
widget annotation that is not linked to any
form field.

Normally, widget annotations carry a reference to a
form field which are used together to implement the
different form widgets. But, the PDF spec does not
forbid standalone (i.e. not linked to any form field)
widget annotations, and the fact is they're been used
by most pdf readers to show a tooltip when the area
of that AnnotWidget is hovered.

The text used for the tooltip is the one in the 'TU'
field (if present) of the widget annotation.

This 'TU' field is mentioned on the PDF spec to carry
an alternative name for the widget, so we named the
new api on that:

  bool standAlone();
  const GooString *getAlternateName();
  bool setAlternateName(const GooString *altName);

The standAlone() method just tell us if this AnnotWidget
is not linked to any form field, and thus we may proceed
to read the 'TU' field if present.

This commit also adds the corresponding poppler-glib api:

gchar   *poppler_annot_get_alternate_name (PopplerAnnot *annot)
gboolean poppler_annot_set_alternate_name (PopplerAnnot *annot,
                                           const gchar  *name)

Fixes issue #34
7 jobs for BUG_tooltip_annots in 6 minutes and 5 seconds (queued for 1 second)
latest
Status Job ID Name Coverage
  Build
passed #1864698
build

00:03:30

passed #1864703
build_android

00:00:51

passed #1864699
build_clang_libcpp

00:03:38

passed #1864702
build_clazy

00:02:31

passed #1874290
build_mingw64_fedora

00:02:27

passed #1864700
build_ubuntu_16_04

00:01:37

failed #1864701
build_mingw64_fedora

00:01:43