Notification level in the user profile does not match Group notification level
<!--IssueSummary start-->
<details>
<summary>
Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards.
</summary>
- [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=362630)
</details>
<!--IssueSummary end-->
<!---
Please read this!
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "regression" or "type::bug" label:
- https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=regression
- https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=type::bug
and verify the issue you're about to submit isn't a duplicate.
--->
### Summary
Notification settings of the group main page not reflected in the user profile notification settings `-/profile/notifications`
### Steps to reproduce
Steps to recreate bug where changing notification of a group also affect its sub group:
1. Create a nested group structure you can go as deep as you like. `Level0` with subgroup `Level1` with subgroup `Level2` .
2. Add a user to the top level group `Level0`. Role does not matter.
3. Now impersonate this user and navigate to the group and change the notification setting.
4. Now navigate to this users `-/profile/notifications` and notice that both `Level0` and `Level1` have changed to the setting changed.
5. Go to the sub group `Level1` directly and notice that the notification setting has not changed here despite being show like that in the users profile.
Other observation:
1. This behaviour can be replicated down the chain.
2. Making changes to notification settings in the user profile makes tis behaviour stop
3. Making changes directly to the subgroup notification setting makes this behaviour stop
What we have also observed in the customer instance is that we were not able to change the notification settings of the Group in the user profile from `watch` to the `global` unless the groups `parent` group notification settings were changed. However I was not able to reproduce this behaviour in my test instance.
For example
* Parent group has `Watch` notification settings and in the user profile notification settings for the subgroup of this parent group it shown as `watch`. When trying to change `subgroup` notification settings in the user profile nothing happens, when you click the notification settings to `global` it always stays as watch after page refresh. The only way the `subgroup` notification setting could be changed from `watch` to `global` if `parent` notification level was changed to `global` in the main page. Note that changing the `subgroup` notification settings to `global` in the main page also did not have any affect on the user notification settings in the profile, it always stayed as `watch` until the notification level of parent group was changed from `watch` to `global` in the main group page.
### What is the current *bug* behavior?
* Notification settings in the User profile notification settings for the group are not reflected in the Group main page.
### What is the expected *correct* behavior?
* Notification settings of the Group main page should reflect in the users notification settings for the Group
*
#### Results of GitLab environment info
GitLab 14.10
### Possible fixes
N/A
GitLab internal [ZD](https://gitlab.zendesk.com/agent/tickets/280440)
issue