Restructure index section (#500)

This will hopefully remove some confusion for users around just showing
off the command vs an example as well as removing examples for index
providers when only one provider exists.

It also updates the links to not mention `administration` as the index
chapter does not live in the administration chapter.

Author: Hunterness

modules/ROOT/pages/clauses/index.adoc

@@ -21,7 +21,7 @@ These comprise clauses used to manage databases, schema and security; further de
 m| xref::administration/databases.adoc[CREATE \| DROP \| START \| STOP DATABASE]
 | Create, drop, start or stop a database.
 
-m| xref::indexes-for-search-performance.adoc#administration-indexes-syntax[CREATE \| DROP INDEX]
+m| xref::indexes-for-search-performance.adoc#indexes-syntax[CREATE \| DROP INDEX]
 | Create or drop an index on all nodes with a particular label and property.
 
 m| xref::constraints/syntax.adoc[CREATE \| DROP CONSTRAINT]

modules/ROOT/pages/deprecations-additions-removals-compatibility.adoc

@@ -3389,7 +3389,7 @@ label:new[]
 DROP INDEX name
 ----
 a|
-xref:indexes-for-search-performance.adoc#administration-indexes-drop-an-index[New command] for dropping an index by name.
+xref:indexes-for-search-performance.adoc#indexes-drop-an-index[New command] for dropping an index by name.
 
 
 a|

modules/ROOT/pages/indexes-for-full-text-search.adoc

@@ -1,6 +1,6 @@
 :description: This chapter describes how to use full-text indexes, to enable full-text search.
 
-[[administration-indexes-fulltext-search]]
+[[indexes-fulltext-search]]
 = Full-text search index
 
 [abstract]
@@ -40,13 +40,13 @@ In contrast to xref::indexes-for-search-performance.adoc[other indexes], a full-
 
 * applied to more than one label.
 * applied to more than one relationship type.
-* applied to more than one property at a time (similar to a xref::indexes-for-search-performance.adoc#administration-indexes-create-a-composite-range-index-for-nodes[_composite index_]) but with an important difference:
+* applied to more than one property at a time (similar to a xref::indexes-for-search-performance.adoc#indexes-create-a-composite-range-index-for-nodes[_composite index_]) but with an important difference:
 While a composite index applies only to entities that match the indexed label and _all_ of the indexed properties, full-text index will index entities that have at least one of the indexed labels or relationship types, and at least one of the indexed properties.
 
 For information on how to configure full-text indexes, refer to link:{neo4j-docs-base-uri}/operations-manual/{page-version}/performance/index-configuration#index-configuration-fulltext[Operations Manual -> Indexes to support full-text search].
 
 
-[[administration-indexes-fulltext-search-manage]]
+[[indexes-fulltext-search-manage]]
 == Full-text search procedures
 
 Full-text indexes are managed through commands and used through built-in procedures, see link:{neo4j-docs-base-uri}/operations-manual/{page-version}/reference/procedures[Operations Manual -> Procedures] for a complete reference.
@@ -89,12 +89,12 @@ Create a relationship full-text index for the given relationship types and prope
 
 | Listing all full-text indexes.
 | `SHOW FULLTEXT INDEXES`
-| Lists all full-text indexes, see xref::indexes-for-search-performance.adoc#administration-indexes-list-indexes[the `SHOW INDEXES` command] for details.
+| Lists all full-text indexes, see xref::indexes-for-search-performance.adoc#indexes-list-indexes[the `SHOW INDEXES` command] for details.
 
 |===
 
 
-[[administration-indexes-fulltext-search-create-and-configure]]
+[[indexes-fulltext-search-create-and-configure]]
 == Create and configure full-text indexes
 
 Full-text indexes are created with the `CREATE FULLTEXT INDEX` command.
@@ -247,7 +247,7 @@ Added 1 index.
 ======
 
 
-[[administration-indexes-fulltext-search-query]]
+[[indexes-fulltext-search-query]]
 == Query full-text indexes
 
 Full-text indexes will, in addition to any exact matches, also return _approximate_ matches to a given query.
@@ -375,7 +375,7 @@ RETURN node.title, node.description, score
 A complete description of the Lucene query syntax can be found in the link:https://lucene.apache.org/core/8_2_0/queryparser/org/apache/lucene/queryparser/classic/package-summary.html#package.description[Lucene documentation].
 
 
-[[administration-indexes-fulltext-search-text-array-properties]]
+[[indexes-fulltext-search-text-array-properties]]
 == Handling of Text Array properties
 
 If the indexed property contains a text array, each element of this array is analyzed independently and all produced terms are associated with the same property name.
@@ -443,10 +443,10 @@ RETURN
 ======
 
 
-[[administration-indexes-fulltext-search-drop]]
+[[indexes-fulltext-search-drop]]
 == Drop full-text indexes
 
-A full-text node index is dropped by using the xref::indexes-for-search-performance.adoc#administration-indexes-drop-an-index[same command as for other indexes], `DROP INDEX`.
+A full-text node index is dropped by using the xref::indexes-for-search-performance.adoc#indexes-drop-an-index[same command as for other indexes], `DROP INDEX`.
 
 
 .+DROP INDEX+