Normalize 'known problems' in RELEASE.txt w/ 1.14

We updated these in the 1.14 branch first, so this just brings the
changes over to develop.

release_docs/RELEASE.txt

@@ -728,7 +728,7 @@ New Features
 Support for new platforms, languages and compilers
 ==================================================
     -
-    
+
 Bug Fixes since HDF5-1.14.0 release
 ===================================
     Configuration:
@@ -2034,12 +2034,12 @@ Platforms Tested
 Known Problems
 ==============
 
-    When building with the NAG Fortran compiler using the Autotools and libtool
+ -  When building with the NAG Fortran compiler using the Autotools and libtool
     2.4.2 or earlier, the -shared flag will be missing '-Wl,', which will cause
     compilation to fail. This is due to a bug in libtool that was fixed in 2012
     and released in 2.4.4 in 2014.
 
-    When the library detects and builds in support for the _Float16 datatype, an
+ -  When the library detects and builds in support for the _Float16 datatype, an
     issue has been observed on at least one MacOS 14 system where the library
     fails to initialize due to not being able to detect the byte order of the
     _Float16 type (https://github.com/HDFGroup/hdf5/issues/4310):
@@ -2054,7 +2054,7 @@ Known Problems
         CMake:      HDF5_ENABLE_NONSTANDARD_FEATURE_FLOAT16=OFF
         Autotools:  --disable-nonstandard-feature-float16
 
-    When HDF5 is compiled with NVHPC versions 23.5 - 23.9 (additional versions may
+ -  When HDF5 is compiled with NVHPC versions 23.5 - 23.9 (additional versions may
     also be applicable) and with -O2 (or higher) and -DNDEBUG, test failures occur
     in the following tests:
 
@@ -2063,50 +2063,51 @@ Known Problems
         H5TEST-testhdf5-base
         MPI_TEST_t_filters_parallel
 
-    Since these tests pass with an optimization level of -O1 (and -O0) and it is
-    currently unclear whether the test failures are due to issues in HDF5 or issues
-    in the 'nvc' compiler, the maximum optimization level for NVHPC has been set
-    to -O1 until the test failures can be resolved. Note that even at -O1 optimization
-    level, there still appears to be a sporadic test failure in the Java JUnit tests
-    that has occasionally been seen in JUnit-TestH5Pfapl and JUnit-TestH5D. It is also
-    unclear whether this is an issue in HDF5 or with the 'nvc' compiler. Finally, note
-    that NVHPC 23.9 will fail to compile the test/tselect.c test file with a compiler
+    Sporadic failures (even with lower -O levels):
+        Java JUnit-TestH5Pfapl
+        Java JUnit-TestH5D
+
+    Also, NVHPC will fail to compile the test/tselect.c test file with a compiler
     error of 'use of undefined value' when the optimization level is -O2 or higher.
-    Nvidia is aware of this issue and has suggested lowering the optimization level to
-    -O1 for the time being:
-    https://forums.developer.nvidia.com/t/hdf5-no-longer-compiles-with-nv-23-9/269045.
 
-    CMake files do not behave correctly with paths containing spaces.
+    This is confirmed to be a bug in the nvc compiler that has been fixed as of
+    23.11. If you are using an affected version of the NVidia compiler, the
+    work-around is to set the optimization level to -O1.
+
+    https://forums.developer.nvidia.com/t/hdf5-no-longer-compiles-with-nv-23-9/269045
+
+ -  CMake files do not behave correctly with paths containing spaces.
     Do not use spaces in paths because the required escaping for handling spaces
     results in very complex and fragile build files.
 
-    At present, metadata cache images may not be generated by parallel
+ -  At present, metadata cache images may not be generated by parallel
     applications.  Parallel applications can read files with metadata cache
     images, but since this is a collective operation, a deadlock is possible
     if one or more processes do not participate.
 
-    The subsetting option in ph5diff currently will fail and should be avoided.
+ -  The subsetting option in ph5diff currently will fail and should be avoided.
     The subsetting option works correctly in serial h5diff.
 
-    Flang Fortran compilation will fail (last check version 17) due to not yet
+ -  Flang Fortran compilation will fail (last check version 17) due to not yet
     implemented: (1) derived type argument passed by value (H5VLff.F90),
     and (2) support for REAL with KIND = 2 in intrinsic SPACING used in testing.
 
-    Fortran tests HDF5_1_8.F90 and HDF5_F03.F90 will fail with Cray compilers greater than
-    version 16.0 due to a compiler bug. The latest version verified as failing was version 17.0.
+ -  Fortran tests HDF5_1_8.F90 and HDF5_F03.F90 will fail with Cray compilers
+    greater than version 16.0 due to a compiler bug. The latest version verified
+    as failing was version 17.0.
 
-    Several tests currently fail on certain platforms:
+ -  Several tests currently fail on certain platforms:
         MPI_TEST-t_bigio fails with spectrum-mpi on ppc64le platforms.
 
         MPI_TEST-t_subfiling_vfd and MPI_TEST_EXAMPLES-ph5_subfiling fail with
         cray-mpich on theta and with XL compilers on ppc64le platforms.
 
         MPI_TEST_testphdf5_tldsc fails with cray-mpich 7.7 on cori and theta.
 
-    File space may not be released when overwriting or deleting certain nested
+ -  File space may not be released when overwriting or deleting certain nested
     variable length or reference types.
 
-    Known problems in previous releases can be found in the HISTORY*.txt files
+ -  Known problems in previous releases can be found in the HISTORY*.txt files
     in the HDF5 source. Please report any new problems found to
     [email protected].