redRQT widget API standardization

Recently we undertook to standardize the redRCore Qt widget API. This is the API that is in the base package.

No elements of the API were removed, standard elements were pushed to be handled by the core widgetState container, which is the universal container for all redR core metawidgets.

All widgets accept the following as key word arguments;

widget - parent widget into which the widget controlArea will be placed.
label - most widgets accept and will display a label, possibly required, and possibly controlled using displayLabel
includeInReports - Indicates if the report generator should include this widget, this is no longer overridden and is exposed to all widgets, though reasonable defaults are set.
toolTip - toolTip is delegated to the widgetState and is available to all widgets.
sizePolicy - all widgets have their control area set to a reasonable sizePolicy, generally this is set to QSizePolicy(QSizePolicy.Preferred, QSizePolicy.Preferred).
whatsThis - all widgets can accept a whatsThis argument used to give additional information for the widget.
styleSheet - sets the style sheet for the widget eg. "QLineEdit {border: 2px solid grey; border-radius: 10px; padding: 0 8px;margin-right:60px; selection-background-color: darkgray;}"
disabled - is the widget disabled (1) or not (0)

By adopting a universal API for widgets and the ability to access and set the widget components should make development and understanding of the core API better. Where possible we shall push API members to the core handler instead of setting them in each widget.

We also implemented several new features that were on the issue list for 1.90. In 1.90 users will be able to set custom variable names for RVariables generated by the widgets. For example, instead of forcing a name_id_timestamp structure, users can rename this to something more understandable to a human reader, for example, myData.