Fix ChangeLog related to new default LLVM features

I submitted emscripten-core#21853 before landing
llvm/llvm-project#80923, so the previous version
(3.1.59) was released before the LLVM change actually landed. And then
we decided to disable reference-types temporarily
(llvm/llvm-project#90792) while the node version
is being resolved
(emscripten-core/emsdk#1173 (comment)).

This moves the entry to the current release and only mentions multivalue
is the newly enabled feature.

ChangeLog.md

@@ -25,17 +25,18 @@ See docs/process.md for more on how version tagging works.
 - The `EXPORTED_FUNCTIONS` list can now include JS library symbols even if they
   have not been otherwise included (e.g. via `DEFAULT_LIBRARY_FUNCS_TO_INCLUDE`).
   (#21867)
+- Due to the upstream LLVM change
+  (https://github.com/llvm/llvm-project/pull/80923 and
+  https://github.com/llvm/llvm-project/pull/90792), multivalue feature is now
+  enabled by default in Emscripten. This only enables the language features and
+  does not turn on the multivalue ABI.
 
 3.1.59 - 04/30/24
 -----------------
 - Fix the location of the dummy `.worker.js` file that is now generated as part
   of pthread builds so that is generated alongside the main JavaScript file.
   See #21701. ()
 - `-sASYNCIFY=2` is setting now deprecated, use `-sJSPI` instead.
-- Due to the upstream LLVM change
-  (https://github.com/llvm/llvm-project/pull/80923), multivalue and
-  reference-types features are now enabled by default in Emscripten. This only
-  enables the language features and does not turn on the multivalue ABI.
 
 3.1.58 - 04/23/24
 -----------------