Remove unused json_events_register route.

The browser registers for events via loading the home view, not this
interface, and this functionality is available via the API-format
register route anyway.

zerver/views/__init__.py

@@ -1159,10 +1159,6 @@ def json_update_active_status(request, user_profile):
 def json_get_active_statuses(request, user_profile):
     return json_success(get_status_list(user_profile))
 
-@authenticated_json_post_view
-def json_events_register(request, user_profile):
-    return events_register_backend(request, user_profile)
-
 # Does not need to be authenticated because it's called from rest_dispatch
 @has_request_variables
 def api_events_register(request, user_profile,

zproject/urls.py

@@ -131,7 +131,6 @@ urlpatterns += patterns('zerver.views',
     url(r'^json/report_narrow_time$',       'report.json_report_narrow_time'),
     url(r'^json/report_unnarrow_time$',     'report.json_report_unnarrow_time'),
     url(r'^json/update_message_flags$',     'messages.json_update_flags'),
-    url(r'^json/register$',                 'json_events_register'),
     url(r'^json/upload_file$',              'json_upload_file'),
     url(r'^json/messages_in_narrow$',       'messages.json_messages_in_narrow'),
     url(r'^json/update_message$',           'messages.json_update_message'),