Fix services user id registration / removal

[dinoboff]

• removed dead code from profile component;
• move service registration logic out of the profile controller;
• automatically create service update task when adding a service (fix Automatically request to update service achievements when services are added to profiles.  #75).
• add firebase test for update request.
• update UI to hide the refresh buttons when the last request was less than 1 minute old (fix Hide the refresh achievements button on profile page for 1 minute after pressing it. #74).
• revert user id claim rules.
• restore button to refresh all services at once.
• add inline doc and unit tests.

TODO:

[dinoboff]

@SingaporeClouds The PR includes some rule changes that will prevent old client to add a services.

The rules enforce a service user id is only used by one user. To add a service:

• you must claim it with /classMentors/servicesUserIds/$serviceId/$serviceUserId set to $publicId
• add service details (id, name and registeredBefore timestamp) at classMentors/userProfiles/$publicId/services/$serviceId with details.id set to $serviceUserId.

We should probably go through each profile and remove service when the user id is shared and add the user id claims otherwise.

* id and name are currently the same value but AFAIK code combat profile have a user name, shown in the code combat profile page and a user id, used to query achievements; We could ask the user a code combat user name and convert it to a user id.

[SingaporeClouds]

There is no reason to prevent users from claiming the same username on a 3rd party service at this point in time. Everyone's username for each service is shown on their profile page, so anyone could quickly determine if someone was using a username that wasn't theirs. Also, if someone accidentally claims someone else's username on Code Combat or FreeCodeCamp by accident (or intentionally), the actual username owner would then be unable to claim their username. The downside of handling these potential disputes at scale is currently greater than the benefit of preventing multiple users from using the same 3rd party username. Therefore, please leave out any rules or mechanisms that try to prevent multiple users from trying to claim the same 3rd party service username.

[coveralls]

Coverage increased (+2.6%) to 10.267% when pulling 0a31d68 on dinoboff:profile-update into b5bab42 on singpath:master.

[coveralls]

Coverage increased (+5.3%) to 12.991% when pulling ca1eaa1 on dinoboff:profile-update into b5bab42 on singpath:master.

[coveralls]

Coverage increased (+5.3%) to 12.991% when pulling 582f0f0 on dinoboff:profile-update into b5bab42 on singpath:master.

[coveralls]

Coverage increased (+5.9%) to 13.583% when pulling 6f766b8 on dinoboff:profile-update into b5bab42 on singpath:master.