Migrate Global blocks branch to latest code

[Toocky]

Issue #1598

#1727 PR with the Global blocks feature was previously approved but never merged and is now outdated and was easier to create a new branch and pull the needed code across.

This was not my code.

The following changes are implemented

Global blocks that can be used and updated on any page for example a navigation bar this eliminates the need to create and updated the same navigation block on all pages

Changes in the user interface:

when creating the block there is a new global block switch

then when adding blocks to a page there is a global blocks drop down selector at the bottom of the Add Blocks modal

Checklist when submitting a final (!draft) PR

• Commits are tidied up, squashed if needed and follow guidelines in CONTRIBUTING.md
• Code builds
• All existing tests pass
• All new critical code is covered by tests
• PR is linked to the relevant issue(s)
• Rebased with the target branch

A side note is there any dev guidance for testing changes? I found the "make watch" to be extremely slow to the point of unusable but I am potentially not doing something correctly.

[gitguardian]

⚠️ GitGuardian has uncovered 2 secrets 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.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
1608142	Triggered	Generic Password	6b877a5	docker-compose.local.yaml	View secret
-	-	Generic High Entropy Secret	6b877a5	.env.docker.dev	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 secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
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.

---

^{🦉 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.}