Update the options' descriptions of the neo4j-admin commands according to the code (neo4j#1852)

see neo-technology/neo4j#27466,
neo-technology/neo4j#27502, and
neo-technology/neo4j#27550

Author: NataliaIvakina

modules/ROOT/pages/backup-restore/aggregate.adoc

@@ -71,7 +71,7 @@ Aggregates a chain of backup artifacts into a single artifact.
 |Accepts either a path to a single artifact file or a folder containing backup artifacts.
 
 When a file is supplied, the _<database>_ parameter should be omitted.
-The option to supply a file is only available from Neo4j 5.2 onwards.
+It is possible to aggregate backup artifacts from AWS S3 buckets, Google Cloud storage buckets, and Azure buckets using the appropriate URI as the path.
 |
 
 |-h, --help

modules/ROOT/pages/backup-restore/offline-backup.adoc

@@ -82,6 +82,7 @@ The `neo4j-admin database dump` command has the following options:
 
 |--to-path=<path>
 |Destination folder of a database dump.
+It is possible to dump databases into AWS S3 buckets, Google Cloud storage buckets, and Azure buckets using the appropriate URI as the path.
 |
 
 |--to-stdout

modules/ROOT/pages/backup-restore/online-backup.adoc

@@ -174,7 +174,7 @@ Note: this is an EXPERIMENTAL option. Consult Neo4j support before use.
 |
 
 |--to-path=<path>
-|Directory to place backup in (required unless `--inspect-path` is used).
+|Directory to place backup in (required unless `--inspect-path` is used). It is possible to back up databases into AWS S3 buckets, Google Cloud storage buckets, and Azure using the appropriate URI as the path.
 |
 
 |--type=<type>

modules/ROOT/pages/backup-restore/restore-backup.adoc

@@ -79,6 +79,7 @@ neo4j-admin database restore [-h] [--expand-commands]
 |--from-path=<path>[,<path>...]
 |A single path or a comma-separated list of paths pointing to a backup artifact file.
 An artifact file can be 1) a full backup, in which case it is restored directly or, 2) a differential backup, in which case the command tries first to find in the folder a backup chain ending at that specific differential backup and then restores that chain.
+It is possible to restore backups from AWS S3 buckets, Google Cloud storage buckets, and Azure buckets using the appropriate URI as the path.
 |
 
 |-h, --help

modules/ROOT/pages/backup-restore/restore-dump.adoc

@@ -77,6 +77,7 @@ If `--info` is specified, then the database is not loaded, but information (i.e.
 
 |--from-path=<path>
 |Path to directory containing archive(s).
+It is possible to load databases from AWS S3 buckets, Google Cloud storage buckets, and Azure bucket using the appropriate URI as the path.
 |
 
 |--from-stdin

modules/ROOT/pages/tools/neo4j-admin/neo4j-admin-import.adoc

@@ -240,6 +240,8 @@ Therefore, use it with care, especially with large imports.
 * Multiple data sources like these can be specified in one import, where each data source has its own header.
 * Files can also be specified using regular expressions.
 
+It is possible to import files from AWS S3 buckets, Google Cloud storage buckets, and Azure buckets using the appropriate URI as the path.
+
 For an example, see <<import-tool-multiple-input-files-regex-example>>.
 |
 
@@ -274,6 +276,8 @@ The value can be a plain number or a byte units string, e.g. `128k`, `1m`.
 * Multiple data sources like these can be specified in one import, where each data source has its own header.
 * Files can also be specified using regular expressions.
 
+It is possible to import files from AWS S3 buckets, Google Cloud storage buckets, and Azure buckets using the appropriate URI as the path.
+
 For an example, see <<import-tool-multiple-input-files-regex-example>>.
 |
 
@@ -292,7 +296,7 @@ This is done by using the `--verbose` option.
 |import.report
 
 |--schema=<path> label:new[Introduced in 5.24] label:enterprise[Enterprise edition]
-|File in which to store the Cypher schema commands to run as part of the data import.
+|Path to the file containing the Cypher commands for creating indexes and constraints during data import.
 |
 
 |--skip-bad-entries-logging[=true\|false]
@@ -751,6 +755,8 @@ Therefore, use it with care, especially with large imports.
 * Multiple data sources like these can be specified in one import, where each data source has its own header.
 * Files can also be specified using regular expressions.
 
+It is possible to import files from AWS S3 buckets, Google Cloud storage buckets, and Azure buckets using the appropriate URI as the path.
+
 For an example, see <<import-tool-multiple-input-files-regex-example>>.
 |
 
@@ -781,6 +787,8 @@ The value can be a plain number or a byte units string, e.g. `128k`, `1m`.
 * Multiple data sources like these can be specified in one import, where each data source has its own header.
 * Files can also be specified using regular expressions.
 
+It is possible to import files from AWS S3 buckets, Google Cloud storage buckets, and Azure buckets using the appropriate URI as the path.
+
 For an example, see <<import-tool-multiple-input-files-regex-example>>.
 |