update migration guide to reflect removal of Vibur + Proxool

Author: gavinking

migration-guide.adoc

@@ -433,6 +433,12 @@ This was incorrect according to the JPA specification, and inconsistent with the
 
 In Hibernate 7, these SQL `UPDATE` statements only occur if the `@OrderColumn` is _not_ also mapped by a field of the entity.
 
+[[pools]]
+== Connection pools
+
+Since Vibur and Proxool are no longer actively developed, support for these connection pools was removed.
+Use Agroal or HikariCP instead.
+
 [[cleanup]]
 == Cleanup
 
@@ -453,6 +459,7 @@ In Hibernate 7, these SQL `UPDATE` statements only occur if the `@OrderColumn` i
 ** Removed `@LazyCollection`
 ** Replaced uses of `CacheModeType` with `CacheMode`
 ** Removed `@TestForIssue` (for testing purposes) -> use `org.hibernate.testing.orm.junit.JiraKey` and `org.hibernate.testing.orm.junit.JiraKeyGroup`
+** Removed `@Cache.include` -> use `@Cache.includeLazy`
 
 * Classes/interfaces
 ** Removed `SqmQualifiedJoin` (all joins are qualified)