Release Notes for 4.0.0-rc.9

[MarkWolters]

This PR gets the ordering and naming of releases correctly for purposes of generating release notes. 4.0.0-rc.9 was released with fixes requested by opensearch team. Next release will be 4.0.1, dropping the "rc" notation. Due to a lack of clarity around these the release note description docs were in the wrong folder and should be moved to the correct one.

This PR also adds release notes documents for all of the included PRs that did not have markdown docs associated with them in the release notes folder. For these PRs the content of the markdown file was copied directly from the PR description. This includes:

• Expose NVQ from its graph feature #693
• Allow bench workflow to run on PRs from forks #688
• Record index build time in buildInMemory path #667
• Add NVQ example #663
• Add offheap memory tracking to Bench YAML reports #671
• Adding memory stats to regression benchmarks #670
• Add openai 1 million vector datasets #669
• Replace __cpuid_check for AVX512 with compiler builtin cpu features #655
• Update regression datasets #658
• Improve performance and checking of recall and precision measurements #647
• Catalog-driven dataset loader #654
• Make benchmark dataset scrubbing metadata-driven and unify HDF5/MFD load behavior #653
• Fix for bug causing tests to use FP vectors in search #645
• add DataSetInfo and some guards around loading errors #637
• Extend benchmark logging to include build and search compressor information #641
• Added link to JV tutorials in the README #644
• Multidirectory #634
• Add quantization timing metrics to YAML benchmarking #636
• Add tutorials and a guide for running benchmarks #617
• Fix file-handle leak by closing BenchmarkDiagnostics (WatchService/inotify) #631
• Introduce run.yml policy and run-scoped experiment logging for Grid benchmarks #625

[github-actions]

Before you submit for review:

• Does your PR follow guidelines from CONTRIBUTIONS.md?
• Did you summarize what this PR does clearly and concisely?
• Did you include performance data for changes which may be performance impacting?
• Did you include useful docs for any user-facing changes or features?
• Did you include useful javadocs for developer oriented changes, explaining new concepts or key changes?
• Did you rebase your branch onto the latest main for regression testing and PR submission?
• Did you trigger regression testing via Run Bench Main and review results?
• Did you adhere to the code formatting guidelines (TBD)
• Did you group your changes for easy review, providing meaningful descriptions for each commit?
• Did you ensure that all files contain the correct copyright header?
• Did you add documentation for this feature to the release notes directory?

If you did not complete any of these, then please explain below.

[jshook]

looks good