CArchive: fix log report introduced in 643133d433bdeb9089c73887391d81dde85c763c
[info] CStdString -> std::string
[info] ToLower() an infobool expression prior to searching to save unnecessary caseless comparisons
[info] splits InfoSingle/Expression out from InfoBool.h
[info] Made CGUIInfoManager::Register() return a shared_ptr to the InfoBool object
rather than an index into its cache of such objects. All places where
those index integers were stored are changed to store shared_ptrs, and
CGUIInfoManager::GetBoolValue() now accepts them instead.

This permits the lifetime of a registered bool to persist across calls of
CGUIInfoManager::Clear(), if necessary.
[controls] GetVisibleCondition is only ever used to check if a visible condition exists, so replace with HasVisibleCondition
[info] use std::find_if() to find previous infobool
[info] ensure we clear the window's conditional includes and visible condition on unload
[info] Add selective caching of infobools in list items

As noted in a TODO comment attached to CGUIInfoManager::GetBoolValue, caching
of infobools (both expression and single bools) is disabled whenever a
CGUIListItem pointer is provided. This is true whenever visibility is
evaluated for a control which is part of a list item (which is responsible
for a large portion of the controls in many windows), which obviously hurts
cache efficiency. However, many of the bools (including the leaf nodes of
expression infobools) aren't actually dependent upon which list item they're
attached to.

This patch adds a flag to each InfoBool object to indicate whether its value
depends upon the list item; if this isn't set, then the cache is re-enabled
even if a CGUIListItem pointer is provided. The flag is calculated at parse
time because it's quite tricky to evaluate - it applies to bools in any of
the following categories:
* a statically definied boolean condition in the range LISTITEM_START to
  LISTITEM_END - for example, "ListItem.IsResumable"
* a (dynamically allocated) multi-info bool, that is to say, the result of a
  string or integer operation on a list item attribute - for example
  "substring(Listitem.mpaa,Rated R)"
* an expression that uses one or more of the above - for example
  "Window.IsVisible(Videos) + !ListItem.IsResumable"

I measured the effect while the Videos window of the default skin was open
(but idle) on a Raspberry Pi, and this reduced the CPU usage by 3.2% from
45.1% to 41.9%:

          Before          After
          Mean   StdDev   Mean   StdDev  Confidence  Change
IdleCPU%  45.1   1.2      41.9   0.5     100.0%      +7.7%
[info] Have the infomanager invalidate infobools so that classes that hold them can call the infobool directly rather than going via the infomanager
[confluence] improving skin code for timer view
[confluence] improving skin code for search view
Merge pull request #3762 from xhaggi/confluence-pvr

[confluence] improve pvr timer and search view
[tests] - fix compile of TestCPUInfo after string changes
[test] - fix compile of TestCharsetConverter after 8f830c1b9a4446f9b68f0dbd693fcda2788eff26
Merge pull request #3775 from jmarshallnz/more_caching_of_bools_in_listitems

More caching of bools in listitems
get rid of two cast warnings
Merge remote-tracking branch 'upstream/master'