Make the cc.xml CCMenu include a Project entry per Branch

[donatj]

CCMenu xml responses are able to include multiple projects. We often have multiple branches running at the same time and right now we only get one ccmenu status back.

This leaves the existing CCProject entry and adds additional Project rows for the individual branches.

It'd be nice for me to be able to just track our dev and master branches separately, so I've altered the cc.go to allow this.

I have not yet altered the tests, I wanted to make sure there was actual interest in doing this first, but I'd certainly be happy to.

[donatj]

I would like to see this one considered.

I corrected the major complaints about breaking backwards compatibility by making the first CCProject entry the same as the existing entry and subsequent entries individual branches. I think that should quell fears.

[bradrydzewski]

Unfortunately I can't see my prior comments, and I apologize if they were vague, but in order to merge the behavior should be opt-in. This means we should preserve the current behavior and only display more branches when specified by a URL parameter.

For example, if ?branch=master,develop

This follows the same behavior as the badges are customized with URL parameters.

[bradrydzewski]

actually, we may end up adding multiple projects to a single repository [1] which could impact this feature. Should probably think through the design implications first. I would hate to merge this and then have to remove it in a future release.

[1] #1021 (comment)

[bradrydzewski]

closing in favor of v1.0 triggers