[Fixes #11316] external pyCSW Service breaks upload of Documents and Datasets

[mwallschlaeger]

This PR is related to #11316 . In my working of trying to bring an external pyCSW service to the geonode-k8s (zalf-rdm/geonode-k8s#34). I'm using the geonode.settings variables: CATALOGUE_ENGINE=geonode.catalogue.backends.pycsw_http and CATALOGUE_URL=http://my-external-pycsw:8000

I stumbled on uploading of documents and datasets wasn't working anymore like described in issue #11316.

So I tracked this down and found some datatype expectations made in geonode/catalgue/backends/generic.py are not working properly. Further I found out that for some reason the contextprocessor for the CATALOG_METADATA_TEMPLATE isn't working inside of the transaction_delete.xml, transaction_update.xml and transaction_insert.xml which lead to a template rendering issue when using an external pyCSW service. So I added this variable through the template context.

This are overall very minor changes.

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: 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.

[codecov]

Codecov Report

Merging #11319 (09c8a0f) into master (4620143) will not change coverage.
Report is 1 commits behind head on master.
The diff coverage is 0.00%.

Additional details and impacted files

@@           Coverage Diff           @@
##           master   #11319   +/-   ##
=======================================
  Coverage   60.61%   60.61%           
=======================================
  Files         867      867           
  Lines       52597    52597           
  Branches     6724     6724           
=======================================
  Hits        31882    31882           
  Misses      19180    19180           
  Partials     1535     1535           

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	Secret	Commit	Filename
-	Django Secret Key	09c8a0f	.env.sample	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

<sup>🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!</sup>