(fast)scan: Solved wierd behavior after removing userbouquets.

When a fastscan or last scanned user bouquet was removed there was some
strange behavior that at a new scan the bouquet did not reappear. You
needed to restart enigma2 before the new bouquet was created and then it
first time this resulted into a bouquets that includes the previous
contants with the new scanned results added, you can even see everything
double.
This was caused because when a userbouquet was removed by the user
interface that only the reference in the rootref was removed.
This solution checks for the reference of a fastscan bouquet or last
scanned bouquet being available in the rootref. When not it will be added
and a new user bouquet will be created or an existing one will be
reopened. When the userbouquet can be created it will always be cleared
first before it is filled with the new scanned services to ensure we do
not have services double or the previous scanned services are still
included.
Revert "(fast)scan: Solved wierd behavior after removing userbouquets."

This reverts commit fbeb8d443d98915180bbfc7d35a22818456915b7.
ChannelSelection: reload bouquets after removal
fastscan: Do not move existing userbouquet to top

Previously I used an extra flag but that made no sense as simply just the
code that moves the bouquet to the top can be removed
cablescan: Do not move existing userbouquet to top
InfoBarGenerics: Correctly set seekstate
Merge remote-tracking branch 'pli/master'