Add a dummy event to left-align results in slider

[mailbackwards]

No description provided.

[mailbackwards]

This is my attempt to fix the centered-image issue with bxSlider. We talked about adding a dummy event with a blank image whenever there is only one result, so that the result will left-align. This code does that by adding a dummy event to the database that can be used anywhere by calling Event.dummy. I did this so that we wouldn't have to work around the Rails serializers and related conventions. But:

• I'm not sure how to avoid it being an active link...it has to have a URL which will then be clickable.
• For the "my favorites" call, I don't think there's an easy way to determine the context of the call (i.e. whether /favorites is being called to get events for the bottom bar or for the "my favorites" page-- If it's the latter, we definitely don't want a dummy event).
• The centered-event problem (and these two issues above) could also theoretically happen on the "near you" and venue pages too. I haven't done anything with those endpoints yet, in part because of these issues.

I'm now wondering whether it might be better practice to append the dummy on the frontend. This would avoid muddying backend logic and a need for a dummy event in the db. I realize it would add to the work for Clearbold but I think it would be feasible for them to do it...and given the issues I raised above, they'd probably need to do some altering of their code anyway to account for these conditionals. @jamiefolsom let's discuss sometime soon.

[mailbackwards]

I just saw this #69. To be continued...

[heymarkreeves]

If it helps, I think we'll initially just force an extra 3 items in every rendering on Staging so that we can evaluate the formatting stuff first, holding off on basing that on dummy API items or conditional logic. Based on where we're at and the items to wrap up, I think I'm as wary of tackling additional conditional logic as you are loading up the API with these until we sort out the interface :)

[mailbackwards]

Updated to address #68 and #69 -- see those issues for discussion of each.