Implement whitelist/blacklist filtering #243
Description
Methods:
cass_execution_profile_set_whitelist_filtering- cass_execution_profile_set_whitelist_filtering_n
- cass_execution_profile_set_blacklist_filtering
- cass_execution_profile_set_blacklist_filtering_n
- cass_execution_profile_set_whitelist_dc_filtering
- cass_execution_profile_set_whitelist_dc_filtering_n
- cass_execution_profile_set_blacklist_dc_filtering
- cass_execution_profile_set_blacklist_dc_filtering_n
- cass_cluster_set_whitelist_filtering
- cass_cluster_set_whitelist_filtering_n
- cass_cluster_set_blacklist_filtering
- cass_cluster_set_blacklist_filtering_n
- cass_cluster_set_whitelist_dc_filtering
- cass_cluster_set_whitelist_dc_filtering_n
- cass_cluster_set_blacklist_dc_filtering
- cass_cluster_set_blacklist_dc_filtering_n
This should probably be implemented using LoadBalancingPolicy, HostFilter and ControlConnectionPolicy (scylladb/scylla-rust-driver#1279) traits. Just LoadBalancingPolicy may not be enough, as in cpp-driver these filters apply for choosing the control connection as well.