[Fixes #12639] Adds all assigned group permissions to user

[ridoo]

This is a quick proposal to ensure a user gets all permissions assigned, including custom permissions which are unknown to GeoNode but potentially created and needed by contrib apps.

See #12639 and #12635 for more details

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"
• PR title must be in the form "[Fixes #<issue_number>] Title of the PR"
• 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: black geonode && 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.

[giohappy]

@ridoo the test suite is failing but it doesn't seem related to your PR. Do you have time to check what's wrong?

[ridoo]

@giohappy thanks for your review!

AFAICS the PR is on top of 'master' which seem to fail similarly:

https://app.circleci.com/pipelines/github/GeoNode/geonode/17373/workflows/b41015bd-12e7-4918-a767-01a918c53853

I was on sick leave yesterday and, unfortunately, will not have time to dig deeper into it next week (which is a short one for me due to upcoming vacation 🥳). I removed the draft status anyway.

[mattiagiupponi]

Hey @ridoo if you merge master in your branch, the test failing unrelated tests should pass 😄

[ridoo]

@mattiagiupponi thanks, should be ready to merge now

EDIT: Any chance to get it backported to v4.3.x?`:)

[giohappy]

Any chance to get it backported to v4.3.x?`:)

@ridoo technically 4.3.x is not supported anymore now that we have 4.4.x. Can't you upgrade?

[ridoo]

Will have to check. Project context, you know?! As there are some major changes I did not dig into yet, I am a bit hesitant. But could also be a chance to catch-up. You can do the merge without waiting on me.