remove internal settings and add Cypher 5 to quarantine database procedure

Author: renetapopova

modules/ROOT/pages/kubernetes/configuration.adoc

@@ -564,11 +564,6 @@ config:
   # Enable automatic reloading of TLS certificates
   dbms.security.tls_reload_enabled: "true"
 
-  # SPeeDy (Sharded Property Database) feature flag
-  # Enables the sharded property database feature for improved performance with large datasets
-  # Set to "true" to enable SPeeDy, "false" to disable (default: false)
-  internal.dbms.sharded_property_database.enabled: "false"
-
 apoc_config: {}
 #  apoc.trigger.enabled: "true"
 #  apoc.import.file.enabled: "true"

modules/ROOT/pages/scalability/sharded-property-databases/admin-operations.adoc

@@ -62,8 +62,6 @@ A backup must be taken of each shard, for example:
 bin/neo4j-admin database backup "foo*" --to-path=/backups --from=localhost:6361 --remote-address-resolution
 ----
 
-The `--remote-address-resolution` option requires `internal.dbms.cluster.experimental_protocol_version.dbms_enabled=true` to be set in both the _neo4j.conf_ and _neo4j-admin.conf_ files.
-
 You can then check the validity of the resulting backups using:
 
 [source,shell]
@@ -130,8 +128,8 @@ Failure to meet this requirement will make a given replica of a property shard u
 If a property shard replica does fall behind the transaction log range available on the graph shard, you can recover it by:
 
 . Connecting to the `system` database on the server hosting the affected replica using the _bolt://_ scheme.
-. Quarantining the replica using xref:procedures.adoc#procedure_dbms_quarantineDatabase[`dbms.quarantineDatabase()`].
-. Unquarantining the replica using xref:procedures.adoc#procedure_dbms_unquarantineDatabase[`dbms.unquarantineDatabase()`] with the `replaceStateReplaceStore` option.
+. Quarantining the replica using xref:procedures.adoc#procedure_dbms_quarantineDatabase[`Cypher 5 CALL dbms.quarantineDatabase()`].
+. Unquarantining the replica using xref:procedures.adoc#procedure_dbms_unquarantineDatabase[`Cypher 5 CALL dbms.unquarantineDatabase()`] with the `replaceStateReplaceStore` option.
 This will force the replica to copy the database store files from another replica of the property shard.
 
 If all replicas of a given property shard are behind, then the sharded property database as a whole becomes unusable.

modules/ROOT/pages/scalability/sharded-property-databases/limitations-and-considerations.adoc

@@ -128,10 +128,4 @@ A suitable heuristic is to ensure that the transaction log kept covers the trans
 [NOTE]
 ====
 It is important to ensure that there is space for the transaction logs and that the server does not run out of disk space.
-====
-
-
-=== Controlling the property shard transaction log pull frequency
-
-The interval at which property shards pull transaction log entries from the graph shard is controlled by `internal.dbms.sharded_property_database.property_pull_interval` (defaults to 10ms).
-Write performance can often be improved by setting this value lower at the cost of more polling on the graph shard from the property shards, however, the impact of this has not yet been fully tested.
+====