Refactor and update the create/find campaign flow

[wdoug]

What does this PR do?

• Refactors the routing code to make it a bit more manageable
• Renames a bunch of components to no longer have the Render prefix
• Deletes a little bit of unused code (There is a bunch more that could probably be deleted)
• Splits logic that used to be in FirebaseChooseCampaign.js into two separate routes that are redirected to after the firebase search returns (I believe this closes Create campaign state flash after create new campaign #441)
  • handleRedirectToExistingCampaign => redirects to new /existing-campaign route
  • handleRenderNearbyCampaigns => currently not handled (may come back to it in the future)
  • handleRenderNewCampaign => redirects to new /create-campaign route
• Adds a wrapping component for authenticated routes that redirects to an initial login page if the user isn't signed in
• Makes the new /create-campaign route require authentication using the above component (Closes Handle UI for create campaign when not logged in #440)

[hoop71]

• Added NewCampaign container to handle auth state while selecting a campaign
• Cleaned up logic and redirect. Moving Redirect functionality into Redux Actions

Things to look for. Does the routing work in different auth states. Does FirebaseInitialSearch or other parts of the store need to be cleared at any point>

[dwhite96]

Everything looks good as far as I can tell.

[julian009]

Solid work on the routing refactor. Everything seems to be working as expected. A couple things we may want to polish off before merging into master/production:

• Add styles to Login component
• Maybe: In the case where a user is not logged in but tries to access a protected route, should the AuthenticatedRoutes component first pop off the most recent protected route from the router stack before pushing the Login path on top? This way when a user tries to navigate backward after being redirected to the Login screen by using the back button of the browser, they will go to the route that they were on before attempting to access the protected route instead of navigating back to the protected route and immediately being redirected to Login again.