EFM 4.10 Changes

This commit pushes just the release note changes so they are available for product management review.

product_docs/docs/efm/4/efm_rel_notes/01_efm_410_rel_notes.mdx

@@ -0,0 +1,13 @@
+---
+title: "Version 4.10"
+---
+
+Enhancements, bug fixes, and other changes in EFM 4.10 include:
+
+| Type | Description |
+| ---- |------------ |
+| Enhancement | Failover Manager was upgraded to use the Bouncy Castle cryptographic library version 1.0.2.5. |
+| Bug Fix | Improve handling of rare case where the standby to promote becomes unavailable during a switchover. [Support ticket: #37266] |
+| Bug Fix | The `efm upgrade-conf` command will not lose .nodes file information when the `-source` and destination directories are the same. [Support ticket: #37479] |
+| Bug Fix | Fixed an issue where the `efm cluster-status` command hid connection errors if every database connection failed. [Support ticket: TBD] |
+| Bug Fix | At startup, if an agent with a primary database sees that there is already a primary in the cluster, it will drop the VIP if applicable when fencing off the database. |

product_docs/docs/efm/4/efm_rel_notes/index.mdx

@@ -6,6 +6,7 @@ cover what was new in each release.
 
 | Version | Release Date |
 | ------- | ------------ |
+| [4.10](01_efm_410_rel_notes) | 15 Aug 2024|
 | [4.9](01_efm_49_rel_notes) | 14 May 2024|
 | [4.8](02_efm_48_rel_notes) | 15 Nov 2023|
 | [4.7](03_efm_47_rel_notes) | 20 Jun 2023|