Branch sample data is incomplete and sometimes confusing

[Jonathan Lange]

Some tasks:

1. Rename '~name12/gnome-terminal/mirrored' to '~name12/gnome-terminal/pulled-and-not-scanned'. The branch is a hosted branch and it exists in the sample data in order to demonstrate the display of a branch that has been pulled using the 'supermirror-pull.py' script, but not yet scanned.

2. Set the last_mirrored time on at least one mirrored branch in the sample data.

3. Make sure all URLs point to 'example.com' or example.com subdomains.

4. Remove branches that aren't needed.

5. Populate the whiteboard text of branches to indicate why the branch is in the sample data.

[Michael Hudson-Doyle (mwhudson)]

There is some more here:

 - adding a branch breaks a few tests, and if you're foolish enough to call your new branch "trunk" it breaks even more

 - not strictly branch related, but the vcs import data (mostly on productseries) is inconsistent and incomplete too