CassandraDataAutoConfiguration's constructor should not require a CqlSession connection

[tmoschou]

The constructor for CassandraDataAutoConfiguration requires a CqlSession connection (provided in CassandraAutoConfiguration) whether used or not. This should be better provided through @Bean method injection which are behind a @ConditionalOnMissingBean.

This means that applications with Cassandra libraries on the Classpath will automatically require a connection by default even when not used, and will fail to boot if a connection cannot be established.

Using Spring Boot 3.2.3

Relates to #11325

[tmoschou]

Ah realised that solution is still not quite right as the beans making use of CqlSession are by default not lazy initialized, unlike CqlSession itself. Feel free to close this ticket.