Add all remaining BUSL change dates + change licenses

dosp-survey.ltx

@@ -166,10 +166,6 @@ used for MaxScale 2.1.0.
 
 BUSL requires a licensor to specify a ``Change Date" and a ``Change License".
 
-How long are the delay periods typically?
-
-What are the eventual OSS "destination" licenses are?
-
 The Linux Foundation noted (https://www.linuxfoundation.org/blog/how-open-source-foundations-protect-the-licensing-integrity-of-open-source-projects)
 that several prominent projects switched away from open-source licenses
 from 2018 to 2023. Not all of these adopted DOSP licenses, but those that did
@@ -189,13 +185,26 @@ Change Date: release +4 years
 Change License: MPL 2.0
 
 Akka (2022-09-07)
+Change Date: release +3 years
+Change License: Apache License, Version 2.0
 \otsurl{https://www.lightbend.com/blog/why-we-are-changing-the-license-for-akka}
 
-Change Date:          TBD ( 3 years after 2.7.0 release )
-Change License:       Apache License, Version 2.0
+ArangoDB
+Change Date: release +4 years
+Change License: Apache License, Version 2.0
+\otsurl{https://arangodb.com/2023/10/evolving-arangodbs-licensing-model-for-a-sustainable-future/}
 
-Sentry (2019-11-06)
+CockroachDB
+Change Date: release +3 years
+Change License: Apache License, Version 2.0
+\otsurl{https://www.cockroachlabs.com/docs/stable/licensing-faqs#bsl}
+
+CouchBase
+Change Date: release +4 years
+Change License: Apache License, Version 2.0
+\otsurl{https://www.couchbase.com/blog/couchbase-adopts-bsl-license/}
 
+Sentry (2019-11-06)
 Change Date: release +3 years
 Change License: Apache License, Version 2.0