[Fixes #9114] Group managers are assigned Manage permission on adding a group with any permission in share permissions form

[afabiani]

References: #9114

Note: The second part of this issue is superseded by #9115

Checklist

Reviewing is a process done by project maintainers, mostly on a volunteer basis. We try to keep the overhead as small as possible and appreciate if you help us to do so by completing the following items. Feel free to ask in a comment if you have troubles with any of them.

For all pull requests:

• Confirm you have read the contribution guidelines
• You have sent a Contribution Licence Agreement (CLA) as necessary (not required for small changes, e.g., fixing typos in the documentation)
• Make sure the first PR targets the master branch, eventual backports will be managed later. This can be ignored if the PR is fixing an issue that only happens in a specific branch, but not in newer ones.

The following are required only for core and extension modules (they are welcomed, but not required, for contrib modules):

• There is a ticket in https://github.com/GeoNode/geonode/issues describing the issue/improvement/feature (a notable exemption is, changes not visible to end-users)
• The issue connected to the PR must have Labels and Milestone assigned
• PR for bug fixes and small new features are presented as a single commit
• Commit message must be in the form "[Fixes #<issue_number>] Title of the Issue"
• New unit tests have been added covering the changes, unless there is an explanation on why the tests are not necessary/implemented
• This PR passes all existing unit tests (test results will be reported by travis-ci after opening this PR)
• This PR passes the QA checks: flake8 geonode
• Commits changing the settings, UI, existing user workflows, or adding new functionality, need to include documentation updates
• Commits adding new texts do use gettext and have updated .po / .mo files (without location infos)

Submitting the PR does not require you to check all items, but by the time it gets merged, they should be either satisfied or inapplicable.

[codecov]

Codecov Report

Merging #9118 (36e7add) into master (a9f7db5) will decrease coverage by 0.00%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #9118      +/-   ##
==========================================
- Coverage   60.71%   60.71%   -0.01%     
==========================================
  Files         805      805              
  Lines       49294    49295       +1     
  Branches     7589     7590       +1     
==========================================
  Hits        29931    29931              
  Misses      17702    17702              
- Partials     1661     1662       +1     

[marthamareal]

@afabiani on testing this, I can still replicate the issues

• Managers of a group(this group is not related to the resource or owner) are given Manage permissions regardless of the assigned permission.
• promotion, demotion, and removal of members (resource group, and owner group dont affect permissions)
• When a group is removed from the resource(managers of the removed group still have their mange perms on the re)

[afabiani]

@marthamareal see below

@afabiani on testing this, I can still replicate the issues

• Managers of a group(this group is not related to the resource or owner) are given Manage permissions regardless of the assigned permission.

This one is fixed by #9119

• promotion, demotion, and removal of members (resource group, and owner group dont affect permissions)

This is wanted as far as I understood on AUTO_PUBLISHING

• When a group is removed from the resource(managers of the removed group still have their mange perms on the re)

This is wanted as far as I understood on AUTO_PUBLISHING