Update dependency matrix-protection-suite to v6

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
matrix-protection-suite	^3.12.0 → ^3.12.0 || ^6.0.0

---

Release Notes

Gnuxie/matrix-protection-suite (matrix-protection-suite)

v6.0.0

Compare Source

Changed

• ServerConsequences is no longer a generic capability provider and is now specific
  to the ServerBanSynchronisationProtection (as it should have been all along).
  The capability providers associated with the interface have now been renamed
  which is a breaking change.

• The ServerBanSynchronisationProtection now depends on its own intent projection
  for producing ACL updates.

Added

• SemanticType abstraction in attempt to get the benefits of TDD without creating
  meaningless tests. I don't mean to imply that TDD leads to meaningless tests, but
  this abstraction helps ensure that all tests are created in relation to an interface
  type and their reason to exist is documented. As well as focussing on checking the
  behavioural contracts that are normally implicit to interfaces. So it's an interesting feature.

• HandleRegistry abstraction to help modularise the "glue code" that sticks
  protection handles up to their data sources. This is particularly important
  because this glue code normally involves resource management (because listeners
  are resources). And it's bad if resource management code exists in an ad-hoc way.
  Handles are described with a HandleDescription, which are then placed into
  a HandleRegistryDescription which describes the handles available for a specific
  context type. And then a HandleRegistry which helps bind the handles for
  a specific context and for specific plugins.

v5.1.0

Compare Source

Added

• Generalised the various variations of the revision issuer abstraction into a Projection interface.

• Added Intent projections for the MemberBanSynchronisation and ServerBanSynchronisation standard
  protections. These show what the protections intend to effect with capabilities before
  capabilities attempt to realise that intent. Think of them as the effect and the capabilities
  as the effect handler.

• All protections can make use of intent projections but obviously migrating the logic
  will take some time. Especially as the upstream revision issuers have not been migrated
  to projections and may be missing detail that is normally fetched from protection's
  arbitrary hooks. It's important to note that the intent projections are deterministic.
  Whereas protections typically have non-determinism mixed within them. To work around
  these instances you will have to make input projections to act as sources of non
  determinism. And this keeps all non determinism at the sources or sinks of the dataflow
  within MPS.

• Lifetimes now have ease of use methods for allocating implementations of the
  ``Symbol.dispose/Symbol.asyncDispose` methods.

v5.0.0

Compare Source

Changed

• Lifetime abstraction introduced for resource management. Is meant to replace
  adhoc unregisterListener methods. the-draupnir-project/planning#79. Protection
  contructor API has been broken as a result as all protections now get a child
  Lifetime from the ProtectionManager that they can atomically allocate resources
  against.

v4.1.0

Compare Source

Changed

• Protection settings are now stored before enabling the protection when
  protection settings are changed. This is to prevent error loops when protections
  modify their own settings.

v4.0.0

Compare Source

Changed

• PermalinkSchema has been split into different schema for each kind of
  matrix.to url. This wasn't done before because we didn't know how to make
  a TypeBox transforms for the same base type work in a union.

v3.13.0

Compare Source

Added

• RoomVersionMirror['privilidgedCreators'] method for fetching creators from
  the create event.

---

Configuration

📅 Schedule: Branch creation - "" in timezone UTC, 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.