[SPARK-53760][GEO][SQL][FOLLOWUP] Fix error message and comment for Spatial types

### What changes were proposed in this pull request?

- Fix the `ST_INVALID_SRID_VALUE` error message.
- Fix the `SpatialType` doc comment.

### Why are the changes needed?
Followup PR to clean up original issues introduced in: #52491.

### Does this PR introduce _any_ user-facing change?
Yes, the `ST_INVALID_SRID_VALUE` error message is updated.

### How was this patch tested?
Existing tests are sufficient.

### Was this patch authored or co-authored using generative AI tooling?
No.

Closes #52632 from uros-db/geo-logical-types-FOLLOWUP.

Authored-by: Uros Bojanic <uros.bojanic@databricks.com>
Signed-off-by: Wenchen Fan <wenchen@databricks.com>

Author: uros-db

common/utils/src/main/resources/error/error-conditions.json

@@ -5573,7 +5573,7 @@
   },
   "ST_INVALID_SRID_VALUE" : {
     "message" : [
-      "Invalid or unsupported SRID (spatial reference identifier) value: <srid>"
+      "Invalid or unsupported SRID (spatial reference identifier) value: <srid>."
     ],
     "sqlState" : "22023"
   },

sql/api/src/main/scala/org/apache/spark/sql/types/SpatialType.scala

@@ -22,7 +22,7 @@ import org.apache.spark.sql.types.AbstractDataType
 trait SpatialType extends AbstractDataType {
 
   /**
-   * Mixed SRID value and the corresponding CRS for geospatial types (Geometry and Geography)
+   * Mixed SRID value and the corresponding CRS for geospatial types (Geometry and Geography).
    * These values represent a geospatial type that can hold different SRID values per row.
    */
   final val MIXED_SRID: Int = -1