Decouple membership and notifications

This allow you to have notification setting per project even if you are member of group. It also creates background for having notification settings in project you are not member of.

• Make it work
• Migrations
• CHANGELOG
• More tests
• API

For #3359 (closed)

After this merge request there is still some work to be done:

• create migration that remove duplicates in notification settings table and create uniq index (8.8 probably)
• remove notification_level field from Member model in 9.0
• make proper API for notification settings
• use MemberCreateService instead of Member#after_create callback for creating notification settings (after #14709 (moved))
• maybe more tests

Signed-off-by: Dmitriy Zaporozhets dmitriy.zaporozhets@gmail.com

app/views/profiles/notifications/show.html.haml

@@ -65,7 +65,7 @@
       %h5
         Projects (#{@project_notifications.count})
       %p.account-well
-        To specify the notification level per project of a group you belong to, you need to be a member of the project itself, not only its group.
+        To specify the notification level per project of a group you belong to, you need to visit project page and change notification level there.
       .append-bottom-default
         %ul.bordered-list
           - @project_notifications.each do |setting|