Problem Statement/Rationale

If you connect to a cluster with in-use connection without storing the provider key (the recommended and default behavior) and then re use the saved connection (either from recents or favorited connection), you'll be able to connect with in-use encryption being in a weird state, leading to any attempt at fetching documents for a collection that has encryption hanging Compass window forever.

See this thread for some additional context

Steps to Reproduce

• Start a replicaset with mongodb 6
• Create a collection with in-use encryption applied
• Connect to cluster in Compass and add a document to the collection
• Disconnect / open "New connection" window
• Connect to the same cluster using "Recent" connection
• Open collection with the document

Expected Results

• You see the document

Actual Results

• Window will hang "forever"

Additional Notes

Seems like validation for the KMS providers kicks in only when you start editing the fields, maybe that's true for other fields too? We probably want the validation to not be coupled just to editing fields in the form