Compliance should be named compatibility (or similar)

This bug is purely about naming. Currently, there is a layer with features equivalent to Kaldi implementations named compliance. I would argue that this is an error in diction. The definition of the word compliance I looked up is, "the state or fact of according with or meeting rules or standards." Kaldi is not a rule or standard; it's a specific technology. I believe the more accepted diction would likely be compatibility. The word compatibility has the definition, "the ability of one computer, piece of software, etc. to work with another." This is also the term that was used in the numpy compatibility project that @umanwizard and @gchanan ran.

Whether we address this issue in torchaudio specifically, I think we are likely to continue to define future compatibility layer-type features, and we should attempt to use consistent language for such features, to help users understood what is the contract of any such component.

Cc @vincentqb @cpuhrsch for discussion

Start by locating the torchaudio layer currently named compliance and review how its Kaldi-equivalent features are exposed. Resolve whether compatibility or another term is preferred before tracing all related references. Done means the agreed terminology is applied consistently across the affected component.