Why was SpecificationVersionDetector moved to test in 2.0?

[moonfruit]

Why was SpecificationVersionDetector moved to the test module in 2.0?
Previously, this class was part of the main source set and could be used by other components at runtime. Moving it to the test scope may indicate it’s now considered internal or only used for validation purposes. It would be helpful to clarify whether this change affects any public API or integration points.

[justin-tay]

It is now internal and largely used to set the default specification version based on path.

[FWest98]

I have a similar question. In my usecase, I want all my schemas to explicitly specify a dialect, so I do not want to provide a default dialect for my schema registry. Previously, I used the version detector to achieve this, but now it seems like I have to specify a default always. Is there a way around it?

[sschuberth]

I believe this should be reopened as PR #1212 IMO did not address this issue.