Remove the 'experimental' marking from vector fields. (#49120)

We wrapped up the API changes we wanted to make, and vector fields can now be
considered GA.

docs/reference/mapping/types/dense-vector.asciidoc

@@ -6,8 +6,6 @@
 <titleabbrev>Dense vector</titleabbrev>
 ++++
 
-experimental[]
-
 A `dense_vector` field stores dense vectors of float values.
 The maximum number of dimensions that can be in a vector should
 not exceed 1024. A `dense_vector` field is a single-valued field.
@@ -53,4 +51,4 @@ PUT my_index/_doc/2
 
 Internally, each document's dense vector is encoded as a binary
 doc value. Its size in bytes is equal to
-`4 * dims + 4`, where `dims`—the number of the vector's dimensions.
+`4 * dims + 4`, where `dims`—the number of the vector's dimensions.

docs/reference/mapping/types/sparse-vector.asciidoc

@@ -7,7 +7,6 @@
 ++++
 
 deprecated[7.6, The `sparse_vector` type is deprecated and will be removed in 8.0.]
-experimental[]
 
 A `sparse_vector` field stores sparse vectors of float values.
 The maximum number of dimensions that can be in a vector should
@@ -61,4 +60,4 @@ PUT my_index/_doc/2
 Internally, each document's sparse vector is encoded as a binary
 doc value. Its size in bytes is equal to
 `6 * NUMBER_OF_DIMENSIONS + 4`, where `NUMBER_OF_DIMENSIONS` -
-number of the vector's dimensions.
+number of the vector's dimensions.

docs/reference/vectors/vector-functions.asciidoc

@@ -3,8 +3,6 @@
 [[vector-functions]]
 ===== Functions for vector fields
 
-experimental[]
-
 NOTE: During vector functions' calculation, all matched documents are
 linearly scanned. Thus, expect the query time grow linearly
 with the number of matched documents. For this reason, we recommend