Update version to 2.3.0

[jammar1]

Hi,

I am proposing to release a new version of WAMR given the large number of changes since the previous release.

I've only bumped the patch number as I can't see any large breaking changes.

I've ignored a few commits where large PRs weren't squashed etc.

Let me know your thoughts about whether the commits are in the right category / whether other commits should be in the "New features" section etc.

Thank you

[lum1n0us]

https://github.com/bytecodealliance/wasm-micro-runtime/blob/main/doc/stability_release.md#release-process

Also need to update build-scripts/version.cmake.

@loganek Do we want to include anything as a sort of experiment in this release to test our ideas regarding Predictable and (almost) fully automated WAMR releases?

[lum1n0us]

belows are required:

• Keep fix the CMake compatibility issue #4180
• Raise wasi-sdk to 25 and wabt to 1.0.37 #4187
• Ubuntu 20.04 LTS (CI) runner will be removed #4186
• SIMD support on windows? #4206,Adjust SIMD* compilation flags to satisfy both fast-interpreter and AOT on Windows #4216
  • Refactor fast-interpreter SIMD compilation flags #4261
  • Check for WASM_ENABLE_SIMDE in a couple more places #4266
• build-scripts/build_llvm.py: bump to llvm 19 #4213 build-scripts/build_llvm.py: bump to llvm 18 #4259 (comment)
  • product-mini/platforms/windows: set C++17 explicitly #4269
  • Set CMAKE_OSX_SYSROOT when building lldb #4274
  • ❓ adapt llvm_wasm.path to llvm-18
• ❓ Add error handling for sgx ci #4222
• Add select 128 #4236
• Bypass wamr_ide-related components from the release process. #4268

[calvin2021y]

please consider fix windows aot related problem in 2.3.0 #4183 #4103

[Zzzabiyaka]

Could we take this onboard please?
#4236

[lum1n0us]

I have rebased onto the main branch.

[kylo5aby]

LGTM

[loganek]

LGTM

[loganek]

main/doc/stability_release.md#release-process

Also need to update build-scripts/version.cmake.

@loganek Do we want to include anything as a sort of experiment in this release to test our ideas regarding Predictable and (almost) fully automated WAMR releases?

Sorry for the late reply. Perhaps we can look into it for the next release.