Refresh UDTs after "keyspace updated" event with v1/v2 protocol
Due to CASSANDRA-7617, when using the v1/v2 protocol, schema change responses and events for UDT changes will appear as "keyspace updated" messages.
The driver should attempt to refresh its view of UDTs whenever we get an event like that and we're using the v1/v2 protocol.
I think we have an issue here.
The problem where the UDT was not added to the metadata in protocol v1/v2 is fixed, but when you drop the udt, those changes are still not reflected in the metadata, with protocol v1/2. (works fine with v3/v4).
I added a test with both protocol versions here. You can run them against a version that supports protocol v1/2 and UDT's like 2.1.x. It will demonstrate the issue.
Test is located on the 106-test branch here.