New "fetched" flag in base collection view

The flag gets set whenever the collection triggers an "add" or a
"reset" event to alert users of the collection that the collection
has already been fetched once.
Woodman traces added to CardPanel and FadeInPanel

The traces help trace the execution of the views and in particular
when transitions start.
Consistent "update" mechanism when model/collection get changed

The "setModel" and "setCollection" methods used to take a second
parameter that forced a complete rendering of the view. That
parameter has now been replaced by a parameter that triggers the
"update" mechanism of the view when the model and/or collection is
modified.

By default, the "update" mechanism forces a complete rendering of
the view but only if needed. For instance:
- for a list, this is when the collection gets changed but not when
individual items in the collection trigger a change, since these
changes get caught by the views that are bound to the element.
- For a dynamic container, changing the number of items in the
collection does not necessarily mean that the "view factory" has to
be called again.
Toolbar: Fixed minLengthToShow mechanism in phone/tv adapters

Note this is just a quick fix to make things work but the mechanism
needs to be revisited later on: a view MUST NOT add classes to
portions of the DOM tree that they do not control and this mechanism
adds a "no-toolbar" class to the <body> tag. Yuck!
TV adapters: isFocusedElement function and Woodman traces added

Within the TV world, the views maintain the view that currently has
the focus in a static variable attached to the TV version of the
UIElement class. The "isFocusedElement" function returns true when
the current view has the focus.

The whole focus/blur mechanism needs to be revisited later on. As
things stand, it duplicates what the browser does and makes things
uselessly complicated. We should rather rely on HTML5 focus features
whenever possible.