Update dependency leaflet.markercluster to v1.5.3

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
leaflet.markercluster	1.4.1 -> 1.5.3

---

Release Notes

Leaflet/Leaflet.markercluster (leaflet.markercluster)

v1.5.3

Compare Source

Bugfixes

• Removing unnecessary files on npm package
• Inlucding correct versioning on Github repo

v1.5.2

Compare Source

Improvements

• Merged PR 1022 for Spiderfy on every room by MasterEric

Bugfixes

• Fixed issue 907 and 967 with PR 1027 from DerGuteWolf
• Removed unexpected dependencies in previous npm package

v1.5.1

Compare Source

Improvements

• Spiderfy on keypress 1005 by @​neorth, a fix for issue 940 and 947

v1.5.0

Compare Source

Bugfixes

• Updated peer dependency to match latest leaflet version (by @​sanjpareek) #​976

(all changes below without author notice were made by @​danzel)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit

File name: yarn.lock

Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit